[GLASSFISH-13982] javax.inject in glassfish repo does not match Maven central repo Created: 14/Oct/10  Updated: 22/Jan/13  Resolved: 22/Jan/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 3.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: pgier Assignee: Romain Grécourt
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 13,982
Tags: 3_1-exclude

 Description   

The javax.inject version 1 jar in the glassfish repository [1] does not match
the same jar in the central Maven repository [2]. The class files in the
glassfish jar are compiled for Java 6 and the class files in the central jar are
compiled for Java 5. Artifacts that have the same GAV (groupId, artifactId, and
version) in a Maven repository should have exactly the same content. Otherwise
you can run into conflicts in the local Maven repository. For example, someone
expecting to download the artifact from central could add the glassfish
repository for some unrelated artifacts and end up with the incorrect file.

[1]http://download.java.net/maven/glassfish/javax/inject/javax.inject/1/
[2]http://repo2.maven.org/maven2/javax/inject/javax.inject/1/



 Comments   
Comment by Sivakumar Thyagarajan [ 14/Oct/10 ]

Adding myself to the interest list

Comment by janey [ 15/Oct/10 ]

The artifacts javax.inject:1 is published to the GlassFish Maven repository because we are doing
source-build for external projects that are referenced in GlassFish v3. The original thought was that
GlassFish is the only recipient of the source-build artifacts. Since Glassfish Maven repository is open
to the community, other project can reference it.

To fix this inconsistency with the central Maven repo, I will remove javax.inject from GlassFish repo.

Comment by pgier [ 15/Oct/10 ]

Just FYI, we've had this same issue come up in the JBoss repository since we
also sometimes rebuild dependency jars. The solution that we came up with is to
give an extra version qualifier to any jars that have been rebuilt. So the
original jar in central might be version 1.0, but our rebuilt jar in the JBoss
repository is version 1.0-jboss-1. This way the GAV is still unique, but it's
clear that these jars are related.

Comment by janey [ 18/Oct/10 ]

Thanks for the suggestion. Our source build requirement is that we don't make any customization to the
build script and source code.

I spoke to Sahoo and we discussed that we will deploy the 3rd party artifacts to our internal Nexus server.
The GlassFish Hudson job will reference the internal Nexus Server. The community GF build should not be
impacted by this change.

Thanks,
Jane

Comment by Romain Grécourt [ 22/Jan/13 ]

download.java.net is not a supported maven repository anymore. See maven central and maven.java.net

Generated at Sat Jul 30 22:48:58 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.