Bug 1377250 - DV 6.2.8: Maven repository contains artifacts of same version with different content than MRRC
Summary: DV 6.2.8: Maven repository contains artifacts of same version with different ...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Distribution
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact: Jan Stastny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 09:55 UTC by Jan Stastny
Modified: 2016-09-19 17:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-19 17:36:13 UTC
Type: Support Patch


Attachments (Terms of Use)

Description Jan Stastny 2016-09-19 09:55:16 UTC
Description of problem:
The following errors we got when testing maven repository for DV 6.2.8 CR2. 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/net/sourceforge/saxon/saxonhe/9.2.1.5/saxonhe-9.2.1.5.jar 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

Comment 1 Alex Szczuczko 2016-09-19 15:52:19 UTC
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 conflicts, but saxonhe-9.2.1.5.jar and jaxb-api-2.1.4.jar aren't in MRRC. So, there's something to fix there.

Comment 2 Alex Szczuczko 2016-09-19 17:36:13 UTC
Actually, the two jboss.org conflicts are not fixable. I must have had the URL wrong when checking for them in MRRC originally, as they are there[1][2].

Looking at jaxb-api-2.1.4.jar, somehow it is f90944f8fb6ef826882b48f7fe315a9d in MRRC, even though the only file in Brew is 63f750861245626b7338e2d2e6a33068 (the jboss.org version). Maybe it came from a local build, or some other untracked source.

For saxonhe-9.2.1.5.jar, MRRC is 18be3fab7b1f924fe4d3305acf789d70, which matches one of two files in Brew (the other is the jboss.org version, b7dd25aa08a639181f5867d9dc6fe1eb). The MRRC version appears to have had the jar signing information removed.

We have to use the MRRC jars, even if they conflict with jboss.org's repo.

[1] https://maven.repository.redhat.com/techpreview/all/sun-jaxb/jaxb-api/2.1.4/jaxb-api-2.1.4.jar
[2] https://maven.repository.redhat.com/techpreview/all/net/sourceforge/saxon/saxonhe/9.2.1.5/saxonhe-9.2.1.5.jar


Note You need to log in before you can comment on or make changes to this bug.