Red Hat Bugzilla – Bug 1026766
Artifacts referenced in eap6-supported-artifacts BOM not available in Maven repository zip
Last modified: 2014-07-03 16:13:05 EDT
Created attachment 819679 [details]
Test pom file
All artifacts referenced in eap6-supported-artifacts BOM are available either in EAP Maven repository zip or in central repository. However the dependency tree cannot be resolved using EAP Maven repository zip only. Following dependencies could not be resolved:
Attaching test pom file with imported all dependencies defined in eap6-supported-artifacts BOM.
Created attachment 819682 [details]
Attaching dependency tree received with enabled central repository.
This issue did not occur in EAP 6.2.0.Beta -- all artifacts referenced in eap6-supported-artifacts BOM were available in EAP Maven repository zip.
This is a regression against 6.2.0 Beta release.
I don't consider this a blocker because we require Maven central for our quickstarts, and our Maven repo zip is not completely self contained. It would require a lot of extra manual POM maintenance to completely remove the dependency on Maven central.
I'm surprised that this wasn't the case in 6.2.0.Beta. Can you attach the dependency tree from 6.2.0.Beta for comparison?
Created attachment 819809 [details]
Dependency tree from 6.2.0 Beta
In the 6.2.0.Beta dep tree it appears there are several transitive dependencies which were not included in the Maven repo zip, so I think this is not a regression. We don't have any plans to fix this because it involves too much manual maintenance of the POMs for each rebuild.
Closing this as won't fix because our current build process relies on Maven central to be available to users. It would require too much maintenance effort to try to modify all poms to use only versions available in the zip, and we would end up shipping artifacts in the zip that we don't want to support (for example the geronimo jars and the spring jars).