I moved IzPack to the Nexus repositories, and it's really as simple as Benjamin mentioned: * make sure you inherit from the Codehaus parent POM at some stage as it contains the repositories references, * use Maven release as usual * go to the Nexus web interface and release from the staging area when it is ok.
Cheers 2010/8/31 Benjamin Bentmann <[email protected]>: > Robert Scholte wrote: > >> The updating of the parent-pom parent isn't the hardest part, but I'd like >> to see that someone with enough experience could update the relevant pages >> and instruct the mojo-team. > > Not sure whether I fully understand your concern but I think most of the > documentation can be copied or just linked from [0, 1] and related. > > Once the Mojo parent uses the staging service, the new process for a release > manager should basically look like: > > 1. run "mvn release:prepare" to create the SVN tag > 2. run "mvn release:perform" to stage the artifacts > 3. log into https://nexus.codehaus.org/ and "Close" the staging repo > 4. send the vote mail to the list > 5. wait > 72 hours > 6. log into https://nexus.codehaus.org/ and "Release" the staging repo > 7. wait some time and find the artifacts synced on central > > The site would be probably be staged as step 2a) by cd'ing into the checked > out tag (target/checkout) and be deployed from there. > > > Benjamin > > > [0] http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven > [1] http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- http://izpack.org/ http://jpz-log.info/ http://julien.ponge.info/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
