Hi Aaron,
I think it would be useful to ask for review the people at
users_at_maven-repository.dev.java.net
Also you can probably ask them how to test it.
Kind regards,
~Jakub
----- Forwarded message from aaronanderson <aaronanderson_at_dev.java.net> -----
Date: Fri, 14 Sep 2007 02:52:02 +0000
From: aaronanderson <aaronanderson_at_dev.java.net>
Subject: [Issue 5] Publish jersey and dependent jars to java.net Maven repositor
To: issues_at_jersey.dev.java.net
https://jersey.dev.java.net/issues/show_bug.cgi?id=5
------- Additional comments from aaronanderson_at_dev.java.net Fri Sep 14 02:52:01 +0000 2007 -------
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe_at_jersey.dev.java.net
For additional commands, e-mail: issues-help_at_jersey.dev.java.net
----- End forwarded message -----