Bug 997877
Summary: | Unavailable artifacts referenced in the main EAP BOM | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Rostislav Svoboda <rsvoboda> | ||||||||
Component: | Maven Repository | Assignee: | Paul Gier <pgier> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikoleta Hlavickova <nziakova> | ||||||||
Severity: | urgent | Docs Contact: | Russell Dickenson <rdickens> | ||||||||
Priority: | unspecified | ||||||||||
Version: | 6.1.1 | CC: | bsutter, kpiwko, myarboro, pslavice, ttarrant | ||||||||
Target Milestone: | ER7 | ||||||||||
Target Release: | EAP 6.1.1 | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-09-16 20:23:27 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Rostislav Svoboda
2013-08-16 11:04:22 UTC
Created attachment 787217 [details]
settings.xml
Created attachment 787218 [details]
jboss-dependency-management-eap-6.1.1.Final-redhat-55.pom-test-pom
Created attachment 787220 [details]
jboss-dependency-management-eap-6.1.1.Final-redhat-55.pom
Thanks for testing this, I should be able to incorporate this into our Maven repo tests. We currently have something similar but it's not as strict. The original requirement was to have the Maven repo zip basically match the contents of the runtime zip. Anything else that is in the repo or in the BOM is only there because of transitive deps or quickstart use cases, so that's kind of the point of view I'm looking at this from. (A) The BOM should be used only for managing the version, since really any of the dependencies could be specified as "POM" type. I think we have to address this one just with documentation of supported use cases. (B) These are not runtime jars, so they are actually not supported, I can remove these from the BOM in the next release. (C) I believe this same issue existed for 6.1.0. For 6.1.1 I can add these transitive dependencies into the repo zip. For 6.2.0, we'll be rebuilding poms so that upstream versions are used for unsupported dependencies. However, the inter-module dependencies are kind of a problem. For example, we support picketbox-infinispan as part of the eap runtime, but not picketbox-spi-bare or jbosssx-bare. Maybe these transitive deps should be marked optional in the picketbox-infinispan pom? Is the problem significantly worse without jboss.org Nexus repo enabled? Ideally, we'd like the repo zip to work with just central. (A) Documentation is not enough, this must be fixed because of customers and layered products. BOM already contains information about type for some artifacts - e.g. jboss-as-ejb-client-bom. (C) Please add missing dependencies and please verify that their dependencies are available too @Nexus I tried to remove nexus repo settings file and executed dependency tree command - FAIL - Could not find artifact org.jboss.naming:jnpserver:jar:5.0.3.GA [DEBUG] org.hornetq:hornetq-jms-server:jar:2.3.4.Final-redhat-1:compile [DEBUG] org.jboss.jbossts:jbossjts:jar:4.16.4.Final:compile [DEBUG] org.jboss.naming:jnpserver:jar:5.0.3.GA:compile So for current issues identified in this BZ we need nexus repo enabled. If we disable it we will have more issues. I was able to get the dependency tree without Nexus enabled - just with Central Maven repo and EAP 6.1.1 ER6 Maven repo. Two more dependencies from test POM file had to be removed, both because of the same artifact org.jboss.naming:jnpserver:jar:5.0.3.GA. The two dependencies are: <dependency><groupId>org.hornetq</groupId><artifactId>hornetq-jms-server</artifactId><type>jar</type></dependency> <dependency><groupId>org.infinispan</groupId><artifactId>infinispan-core</artifactId><type>jar</type></dependency> (A) I will remove the type declaration for those deps from the BOM. It's a bad practice to rely on the BOM to define the type. (C) Yes, I will try to capture the full transitive tree. Is it ok if I add org.jboss.naming:jnpserver:jar:5.0.3.GA and possibly other required jboss.org artifacts to the repo zip? That would allow the bom dependencies to be resolved without the jboss.org repo. > jboss.org artifacts to the repo zip? If we receive ER7 with rebuild of EAP because of HQ we want to have dependencies productized. Including artifacts mentioned in BZ 991358 If we receive ER7 just with maven repo fix and no rebuild in EAP bits we won't consider not productized bits as release blocker. Verified for EAP 6.1.1 ER7. Not productized artifacts are listed in BZ 991358 |