The last two days I've spent some time to prepare the mojo-parent[1] and the documentation with some help from Benjamin Bentmann.
It wasn't all that straight forward (mojo is an extraordinary project ;) ), but we're almost there. Most important is that we've decided to keep our own release-profile instead of the one provided in the codehaus-parent, since we're doing extra stuff. But we added the maven-gpg-plugin, which brought us to a new problem: how to manage these keys, since there are a lot of different developers releasing mojo's. We copied the solution of the apache maven developers group, by introducing a KEYS file [2]. Every time the moj-site is deployed, the KEYS file will be updated in the root of the project-site[3]. Developers must add their public key here before being able to release. All has been documented (not yet published), including how to generate such key. When staging, the order of release-steps change a bit. First you release:prepare and release:perform the project, so it'll be ready to be staged. After that the voting starts. One issue we haven't solved yet concerns the site-deployment. Still by default a release:perform executes both "deploy" and "site:deploy", which means the site is published before the voting has even started. We should somehow split these deployments, but how can we deploy the site once the voting has succeeded? I've checked the codehaus' Nexus instance, but my left pane is very empty (only security and help available). Sounds like a permission thingy, so I've asked Juven to check this. Once I can conform everything should work I'll start a vote for the mojo-parent. In the meantime you could update the KEYS file :) - Robert [1] http://svn.codehaus.org/mojo/trunk/mojo/mojo-parent/pom.xml [2] https://svn.codehaus.org/mojo/site/src/site/resources/KEYS [3] http://mojo.codehaus.org/KEYS (it's not there yet!!) > From: [email protected] > Date: Tue, 31 Aug 2010 09:58:18 +0200 > To: [email protected] > Subject: Re: [mojo-dev] Help requested on staging mojo-projects with Nexus > > 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 > >
