Sandbox plugins should be snapshot revisions. Once a vote has been
called and passed for a release of a plugin in the sandbox, it should
graduate from the sandbox, then make a formal release. Otherwise, the
deploy will put the artifact on ibiblio instead of the snapshots repo. 

-----Original Message-----
From: Allison, Bob [mailto:[EMAIL PROTECTED] 
Sent: Sunday, January 15, 2006 11:02 AM
To: dev@mojo.codehaus.org
Subject: RE: [mojo-dev] Maven2 RPM Plugin "Release"

OK.  I updated the site.xml according to the template (except I kept the
link for Maven as "http://maven.apache.org/"; rather than
"http://maven.apache.org/maven2"; since the latter redirects to the
former).  I also committed the POM with the release version.  Do I have
permission to do a "mvn deploy" to put the jar in place for people to
use and to do "mvn site:deploy" to update the site?

-----Original Message-----
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 15, 2006 10:08
To: dev@mojo.codehaus.org
Subject: RE: [mojo-dev] Maven2 RPM Plugin "Release"


The sandbox parent is already done and all the sandbox plugins have been
updated. The sites are published and the last step is to update the main
site, which I planned for today. The rpm site is basically ready to go.
It just needs the mojo template. Take a look at this page:
http://mojo.codehaus.org/development/site-guidelines.html 

-----Original Message-----
From: Allison, Bob [mailto:[EMAIL PROTECTED] 
Sent: Sunday, January 15, 2006 6:59 AM
To: dev@mojo.codehaus.org
Subject: [mojo-dev] Maven2 RPM Plugin "Release"

Now that the RPM plugin does not depend on uncommitted code in Plexus, I
want to make it more visible on the Mojo website so people can find it
and use it.

Right now, I have the plugin's site and binary distro in my codehaus
home directory (http://www.codehaus.org/~boba/rpm-plugin/intro.html).  I
was going to "release" version 1.0-alpha-2 (since it seems to work
properly for me) and let others give it a try to find out where there
are still problems.  Where do I need to deploy to make the plugin work
properly?  I guess the real question is "How do I set up the
distribution, scm, and url items in the POM so that I get valid
information and can deploy the jar and site properly?"  I heard talk of
a sandbox parent to hold all of this so maybe I just need to alter the
"parent" tag and not specify any of this stuff in my POM.

Also, what files should I update (if I can) so that the RPM plugin
appears in the list(s) of available plugins?  I am referring to the left
sidebar of the Mojo project as well as the plugin list in the Maven
documentation.





Reply via email to