Community
Participate
Working Groups
Created attachment 222340 [details] eclipse.jdt.core.binaries.patch For Tycho to generate Eclipse-SourceReference headers a new property needs to be added to the pom ${tycho.scmUrl} for each repo.
Jay, please follow up, TIA
eclipse.jdt.core.binaries is not intended for installation into the IDE, IIRC this is just a collection of (large) files used by tests. Thus I don't see use in having a Eclipse-SourceReference here. Am I missing anything?
(In reply to comment #2) > eclipse.jdt.core.binaries is not intended for installation into the IDE, > IIRC this is just a collection of (large) files used by tests. > > Thus I don't see use in having a Eclipse-SourceReference here. > Am I missing anything? We set in the eclipse-parent/pom.xml to tell Tycho to set Eclipse-SourceReference and Tycho requires this variable set to build or it will fail with the error below. It would require some restructure of the pom files to tell Tycho which repositories specifically to build. Is there any issue with having this for a package that doesn't need it? [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.16.0-SNAPSHOT:package-plugin (default-package-plugin) on project org.eclipse.jdt.core.tests.binaries: Error assembling JAR: Eclipse-SourceReferences header should be generated but ${tycho.scmUrl} is not set -> [Help 1]
I should have mentioned this should be applied to 3.8.2.
(In reply to comment #3) > (In reply to comment #2) > > eclipse.jdt.core.binaries is not intended for installation into the IDE, > > IIRC this is just a collection of (large) files used by tests. > > > > Thus I don't see use in having a Eclipse-SourceReference here. > > Am I missing anything? > > We set in the eclipse-parent/pom.xml to tell Tycho to set > Eclipse-SourceReference and Tycho requires this variable set to build or it > will fail with the error below. > > It would require some restructure of the pom files to tell Tycho which > repositories specifically to build. Is there any issue with having this for > a package that doesn't need it? Not a problem, just it doesn't feel right if a tool forces us to do stupid things. I'd normally assume this header makes no sense for any of the test plugins, but I'll stop arguing here :)
Released the fix in master and R3_8_maintenance
Verified for 4.2.2 M20130109-1200
I have also verified that this indeed has been fixed in 4.3 M4.