Artifact com.sun.xsom:xsom:jar:20110809-redhat-3 declare dependency on com.github.relaxng:relaxngDatatype:2011.1-redhat-3, which version is defined in org.jboss.component.management:jboss-component-version-master:6.0.1-redhat-1, but this versin isn't in repository, actual version is 2011.1-redhat-6.Same issue is in com.sun.xml.txw2:txw2:20110809-redhat-2.
There is no reaction to this issue, however this seems to slip over CP01, CP02 ?
It's not clear what "repository" in BZ Description means. Could you please specify it? The artifact is available in the MEAD Maven repository for jb-eap-6-rhel-6-build target: http://download.eng.bos.redhat.com/brewroot/repos/jb-eap-6-rhel-6-build/latest/maven/com/github/relaxng/relaxngDatatype/2011.1-redhat-3/ EAP Maven repository zip doesn't contain every transitive dependency especially if it's not the part of build or runtime dependency tree for EAP distribution or any included quickstarts or client BOMs. BOM jboss-component-version-master 6.0.1-redhat-1 is formal component management for building EAP or it's components, originally for EAP 6.0.1. Now it's strictly for backward compatibility and for maven dependency resolving because it's linked in the dependency management in poms of some artifacts/dependencies which have not been upgraded since EAP 6.0.1 and are still in the dependency tree of EAP or quickstarts.
Please check https://issues.jboss.org/browse/WFK2-459 for backward info
Vladimir, it is an artifact missing in EAP Maven repository. In fact it is not missing, but containing the newer version... jboss-eap-6.2.0.GA-maven-repository/com/github/relaxng/relaxngDatatype/2011.1-redhat-6 which is wrongly referenced by another artifacts miss: com.github.relaxng:relaxngDatatype:jar:2011.1-redhat-3 from: org.richfaces.cdk:generator:pom:4.3.1.Final-redhat-4 path: org.richfaces.cdk:generator:pom:4.3.1.Final-redhat-4 > com.sun.xml.bind:jaxb-impl:jar:2.2.5.redhat-7 > com.sun.xml.txw2:txw2:jar:20110809-redhat-2 > com.github.relaxng:relaxngDatatype:jar:2011.1-redhat-3 So, to summarize... EAP 6.2.0 M2 repo contains com.github.relaxng:relaxngDatatype:jar:2011.1-redhat-6 artifact, while others in the same repo are referencing com.github.relaxng:relaxngDatatype:jar:2011.1-redhat-3 HTH
We're not using that BOM (org.jboss.component.management:jboss-component-version-master:6.0.1-redhat-1) anymore. It's still available in Maven repository zip but only for maven dependency plugin resolving and constructing effective pom of EAP/AS during its build. It doesn't mean that all artifacts in this BOM must be included in EAP Maven repository zip. Artifact com.github.relaxng:relaxngDatatype:2011.1-redhat-3 is not on the dependency list/tree of EAP 6.2.x, it was but for earlier release (EAP 6.0.1). It's also not the transitive dependency of additional bits of EAP 6.2.x release such as quickstarts. It's the transitive dependency of some dependencies which are dependencies of EAP directly but it's not resolved as this GAV for EAP. So it's correct it's not zipped in EAP Maven repository zip. It's still in the MEAD Maven repository jb-eap-6-rhel-6-build and available for other products and their builds [BREW]. If you need it, just tag it into your product's Maven repository. [BREW] https://brewweb.devel.redhat.com/buildinfo?buildID=232959
Please contact thradec to share the tool and CI job, which checks the supported GAV tree in Maven repository zip file.
In WFK we use tool wolf-validator, see [1] jenkins job. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/WFK/view/WFK-2.5/job/wfk-2.5-wolf-validator/
The artifact added into manual includes list for generation Maven repository zip for EAP 6.2.x. Will be available in the Maven repository zip (incremental maven repository zip) in the next release. http://git.app.eng.bos.redhat.com/git/jboss-eap/maven-repository-testsuite.git/commit/?id=3dd7190
EAP 6.2.3 Maven repo zip contains artifact com.github.relaxng:relaxngDatatype:2011.1-redhat-3 declared by com.sun.xsom:xsom:jar:20110809-redhat-3