Jason van Zyl wrote:
There are groups there for Maven 2.1, Plexus, Maven IDE (really
embedder consumers), and I will also limit the plugins to the default
lifecycles of the commonly used packagings like JAR, and WAR. John has
also started creating automated ways to release to stage, and
subsequent promotion upon success. So for any component in the tool
chain there will be a way to do a consistent release from a canonical
machine.
Just for posterity (if we're going to be using this as an official
release vector for the entire project):
Jason's referring to a ruby script I wrote to lookup the version string
for a particular staged project, for use in the stage:copy mojo. This
allows us to setup generic promotion scripts in a CI environment like
Hudson. I've committed this script to:
https://svn.apache.org/repos/asf/maven/sandbox/trunk/scripts.
The rest of this release infrastructure has simply been configuration of
hudson and nexus - nexus, to provide a staging ground for releases - to
configure release jobs that deploy to this staging location instead of
the real release repository...just generalizing on configuration that we
all have in our personal settings.xml files by now. Jason's credentials
are used for SVN and SSH where necessary, and I've created a new GPG key
for use in this CI system, then signed it with my own key. That key ID
is: 84B54612.
To echo Jason, the goal here is to create an environment that - if not
perfectly flawless - is at least a known quantity. Just as we've moved
in the direction of pointing to our CI servers as the definitive point
of reference for our unit and integration tests (though we're not quite
there yet), we need to be releasing Maven artifacts from a similarly
definitive environment. In principle, the configuration and script I've
written (above) should enable any team to enable a similar release
infrastructure for their own projects.
-john
I am also working with the Apache Infrastructure team to integrate the
Contegix folks who are the ones who currently host all the hardware
we're using. Maven's central repository, our Hudson instance, and our
Nexus instance. So, in short order, the Contegix hardware will be
official Apache hardware.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
A language that doesn’t affect the way you think about programming is
not worth knowing.
-— Alan Perlis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
