Don't generate a source bundle with only an about.html#1772
Don't generate a source bundle with only an about.html#1772merks merged 1 commit intoeclipse-pde:masterfrom
Conversation
|
Actually I'm not really sure this is the right way. Other places seem to set the property to not generate, but even that seems insufficient and so there also appears to be a need to configure the pom.xml to exclude it: I.e., it appears to be necessary to add |
|
This is related: eclipse-platform/eclipse.platform.releng.aggregator#3038 For the record, these are all bundles that I noticed have source bundle that don't actually contain any useful sources: |
|
Could Tycho be made smarter and not generate source bundles if it identifies no .class file was generated? |
A bundles does not need to contain classes to have sources, e.g. html, images, ... so its a bit a matter of definition and in the past some checks in platform even complained when there is no source bundle at all. I think instead of trying to be smart, it would be easier to add a The second part is about source features what will exclude it from the feature, but as we use |
|
Please advise on the correct/best approach. I'd simply like to eliminate pointless noise... (Of course a source bundle can have an arbitrary content, but the general purpose is to provide sources of corresponding .class files for which there is no corresponding content in the binary bundle, not to duplicate the binary content or simply to exist with no useful information at all.) |
|
If i where to solve it I would go to OsgiSourceMojo and add a new Of course one would add an integration-test to demonstrate use-case and probably find then that other places are not happy when we simply not generate it in the first place :-) |
Created a corresponding PR at |
@merks the required change in Tycho is now available, also as backport to Tycho 4.0.13-SNAPSHOT. Do you want to continue this? |
8834098 to
431b274
Compare
|
The build seems to hang with this failure which looks unrelated to this change. Is this the change you are expecting? I see this in the log Does that tell us anything useful? I think not because in https://ci.eclipse.org/pde/job/eclipse.pde/job/PR-1772/lastSuccessfulBuild/artifact/repository/target/repository/plugins/ I see this What might I be doing incorrectly? |
431b274 to
2a9061d
Compare
|
You should see that the source mojo prints a message that execution was skipped. But if you don't increment the version it might maybe restored from baseline. |
15f425d to
bd1b3a6
Compare
|
Yes if there is a pom (didn't realized that) you need to configure it in the pom in the build section. |
Wouldn't it be sufficient to define it as property in the properties section? I.e. |
bd1b3a6 to
6bd6975
Compare
|
To make sure this doesn't cause downstream problems and correctly produces the expect result in the final p2 repository I kicked off this I-build: https://ci.eclipse.org/releng/job/Builds/job/I-build-4.36/60/ Then I can apply this solution to the other bundle mentioned in #1772 (comment) |






No description provided.