Publish jersey and dependent jars to java.net Maven repositor

[jerseyrobot]

Publish jersey and dependent jars to java.net Maven repositor

[jerseyrobot]

• Issue Imported From: https://github.com/jersey/jersey/issues/277
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @mpotociar
• Original Issue Closed By:@glassfishrobot

[jerseyrobot]

@glassfishrobot Commented
Reported by [email protected]

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
Created an attachment (id=1)
example jersey POM file that cleans and installs the jersey jars in the local maven repository

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
I'd like to assist with the jersey maven support if needed. I'd like to know
which approach you all would like to use for adding jersey to a maven repository.

1. Deploying to the legacy maven repo https://maven-repository.dev.java.net/
This would involve adding maven pom files for the JSR-311 and Jersey jar files
as well as the maven-repository-importer.jar. The ant build file would be
extended to deploy the artifacts to the maven repository.One catch is that the
documentation refers to CVS repositories, I dunno for sure if it would work with
SVN.

2. Same as above but use the maven plugin in the previously attached POM instead
of the ant task.

3. Deploy to the new https://maven2-repository.dev.java.net/ I think I can
easily extend the previously attached POM to deploy to the maven2-repo checkout
directory. It would still probably be beneficial to main the pom files in the
jersey source as the generated POM files do not include any dependencies.

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
When i try the attached [pom.xml], I get:

-cuthere-
Downloading:
http://snapshots.repository.codehaus.org//org/codehaus/mojo/properties-maven-plugin/1.0-SNAPSHOT/properties-maven-plugin-1.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.codehaus.mojo
ArtifactId: properties-maven-plugin
Version: 1.0-SNAPSHOT

Reason: Unable to download the artifact from any repository

org.codehaus.mojo:properties-maven-plugin:pom:1.0-SNAPSHOT

from the specified remote repositories:
central (http://repo1.maven.org/maven2),
Codehaus Snapshots (http://snapshots.repository.codehaus.org/)
-cuthere-

I am using Maven version: 2.0.6
Shall i be using maven v1 instead?

(http://snapshots.repository.codehaus.org//org/codehaus/mojo/properties-maven-plugin/1.0-SNAPSHOT/properties-maven-plugin-1.0-SNAPSHOT.pom
is not available via firefox anyway)

Is my understanding right, that using provided [pom.xml], maven
will automatically download any software needed and build up a local
maven repository for me?

Thanks for your help!

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
that is strange. I just checked out the jersey code from the trunk on a solaris
box, put the pom in trunk/jersey , and ran mvn clean install using maven 2.0.7
without a problem. Can you run mvn -U -cpu clean install and see if that helps?
From the URL it seems maven didn't read the manifest to get the latest version
of the plugin and blindly attempted to download the snapshot without the unique
version ID.

When the install goal is run the project invokes the install plugin and should
install the jsr-311 api as javax.ws.rs jsr311-api 0.2 and the jersey jar file as
net.dev.java.jersey jersey-0.3-SNAPSHOT-ea

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
One more thing, the use of the plugin is optional, I just wanted to pull the
jersey version info from the build.properties and use it for the installing the
jars in the local repository. If the POM can be maintained with the same version
info as the build.properties the use of the properties plugin is no longer
needed and everything can be built using the standard maven plugins.

The properties plugin is stored in the snapshots.codehaus.org repo and I added a
repository entry for it so the plugin should download correctly.

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
Created an attachment (id=2)
version without properties plugin

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
Created an attachment (id=3)
support for publishing jersey.jar and jsr311-api.jar to the java.net maven repository

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
Here is a patch containing the changes mentioned on the dev list. Here is how it
works:

1. When a new release is ready, the releaser runs
ant clean,push-to-maven-prepare
This will generate a local maven repository ready to be published.

2. For the first import, the releaser will run
svn import -m "deploying new jars to the java.net maven repository"
build\maven-repo file:///e:/temp/scmtest/repo/jersey/trunk/repo
This will import the maven repository under the jersey projects /trunk. After
this is done hopefully the maven_repository daemon will receive the source
update notification and publish the repo files to the maven repository web server.

3. After the intial repo import a second import will fail since the repo
directories and files already exist. Before running the import, run the svn
delete command to remove the old binaries.
svn delete -m "preparing for new jar deployment to maven"
https://jersey.dev.java.net/svn/jersey/trunk/repo

That should do it for publishing the Jersey artifacts to the java.net maven
repository. It would probably be a good idea if Kohsuke could review the svn
commands to make sure that svn is support by the daemon and the repo is checked
into the the proper directory.

I included the maven/pom.xml for developers who checkout the Jersey source and
want the latest version of the code installed in their local maven repository.
The developer would change directories to the maven directory and run
mvn install

Finally, all the Jersey core dependencies were already in the java.net
repository except for localizer.jar file. I haven't been able to locate a
java.net project that is associated with it. I was thinking that if the
localizer.jar file is exclusively used by Jersey then it could be added and
maintained with this project the same as the jersey.jar and jsr311-api.jar
artifacts are.

[jerseyrobot]

@glassfishrobot Commented
[email protected] said:
Fixed, thanks to Aaron Anderson.

[jerseyrobot]

@glassfishrobot Commented
File: jersey-maven.patch
Attached By: [email protected]

[jerseyrobot]

@glassfishrobot Commented
File: pom.xml
Attached By: [email protected]

[jerseyrobot]

@glassfishrobot Commented
File: pom.xml
Attached By: [email protected]

[jerseyrobot]

@glassfishrobot Commented
Was assigned to jersey-issues

[jerseyrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA JERSEY-5

[jerseyrobot]

@glassfishrobot Commented
Marked as fixed on Sunday, November 4th 2007, 6:10:34 pm