Hide Forgot
Description of problem: The following errors we got when testing maven repository for DV 6.3.1 CR1. The artifacts are of same grouId, artifactId, version, but have different content: Remote repository [http://maven.repository.redhat.com/earlyaccess/] contains already artifact http://maven.repository.redhat.com/earlyaccess/com/sun/mail/javax.mail/1.4.4-redhat-2/javax.mail-1.4.4-redhat-2-sources.jar with different content Remote repository [http://maven.repository.redhat.com/earlyaccess/] contains already artifact http://maven.repository.redhat.com/earlyaccess/com/sun/mail/javax.mail/1.4.4-redhat-2/javax.mail-1.4.4-redhat-2.jar with different content Remote repository [http://maven.repository.redhat.com/earlyaccess/] contains already artifact http://maven.repository.redhat.com/earlyaccess/org/jboss/component/management/jboss-component-version-master/6.0.1-redhat-1/jboss-component-version-master-6.0.1-redhat-1.pom with different content Remote repository [http://maven.repository.redhat.com/earlyaccess/] contains already artifact http://maven.repository.redhat.com/earlyaccess/org/jboss/jboss-vfs/3.1.0.Final-redhat-2/jboss-vfs-3.1.0.Final-redhat-2-javadoc.jar with different content Remote repository [http://maven.repository.redhat.com/earlyaccess/] contains already artifact http://maven.repository.redhat.com/earlyaccess/org/olap4j/olap4j-xmla/1.1.0/olap4j-xmla-1.1.0.pom with different content Remote repository [http://maven.repository.redhat.com/earlyaccess/] contains already artifact http://maven.repository.redhat.com/earlyaccess/org/olap4j/olap4j/1.1.0/olap4j-1.1.0.pom with different content Remote repository [https://repository.jboss.org/nexus/content/groups/public-jboss/] contains already artifact https://repository.jboss.org/nexus/content/groups/public-jboss/sun-jaxb/jaxb-api/2.1.4/jaxb-api-2.1.4.jar with different content
Unfortunately, I can't do anything about the earlyaccess conflicts, as techpreview contains those files as well, with different content: > javax.mail-1.4.4-redhat-2-sources.jar other: c450c9842e30a8d5ac259a387764d558 mrrc: 8aacedb9f8b6fe747f2294873f808890 > javax.mail-1.4.4-redhat-2.jar other: 62b131fb26e1c8baa3e7c83ffaf98d91 mrrc: c97d75e43e0f06837cae10bff93dc409 > jboss-component-version-master-6.0.1-redhat-1.pom other: c1937b7c8e1fe18e3b10b58594f86bcb mrrc: 7819a7d533d4820ea9ba01d43ca44218 > jboss-vfs-3.1.0.Final-redhat-2-javadoc.jar other: 3db4799c7bbded49126a22ba43a2b9b1 mrrc: 25ca2572c5b3a47462e97bd0ceb2eed6 > olap4j-xmla-1.1.0.pom other: ef8891668acaa4e6c79744f6018885c7 mrrc: 6985f83209a51facd8d569ef5bf0d8ed > olap4j-1.1.0.pom other: 43ccd308abd590aa41e220dd6a02d208 mrrc: bf5136d787a3a4eacfd5f6838c469c10 Initially I thought the same would apply to the jboss.org conflict, but jaxb-api-2.1.4.jar isn't in MRRC. So, there's something to fix there.
See bug 1377250, comment 2.