Description of problem: Eclipse relocated various artifacts under their own groupId - org.eclipse.jetty.orbit. Please additional depmaps to appropriate artifacts in eclipse package. The following artifacts need to have depmaps added with groupId org.eclipse.jetty.orbit: * org.eclipse.jdt.core For more information on how to add extra mappings see Java packaging guidelines[1], especially the part describing %add_maven_depmap macro[3]. Version-Release number of selected component (if applicable): 4.3.0-0.21.git3fd9eca Additional info: [1] http://fedoraproject.org/wiki/Packaging:Java [2] http://fedoraproject.org/wiki/Packaging:Guidelines [3] http://fedoraproject.org/wiki/Packaging:Java#add_maven_depmap_macro
Created attachment 704931 [details] Proposed patch
Created attachment 704960 [details] Proposed patch
The *orbit* names are allowed for names that are not managed by Eclipse foundation, but are from other foundations and are used by Eclipse. The JDT is a core Eclipse bundle, and therefore it should not be mapped to org.eclipse.jetty.orbit: .
Yet eclipse packages (like Jetty 9 RC3, released 3 days ago) require this depmap. ./jetty-9.0.0.RC3/pom.xml- <dependency> ./jetty-9.0.0.RC3/pom.xml: <groupId>org.eclipse.jetty.orbit</groupId> ./jetty-9.0.0.RC3/pom.xml- <artifactId>org.eclipse.jdt.core</artifactId> ./jetty-9.0.0.RC3/pom.xml- <version>3.7.1</version> ./jetty-9.0.0.RC3/pom.xml- </dependency> Please reconsider adding it.
reopening for investigation.
Released the rebased version of a patch. Due to the lack of central Eclipse maven repository, projects started to create their own poms and names. There may be more mappings needed soon. :-(