Re: How to validate a Maven release? Fwd: [VOTE] Release Maven antrun plugin version 1.2

2008-07-20 Thread Arnaud HERITIER
Couldn't we setup a custom profile for QA checks (pmd, checkstyle, clirr ...) that we activate in a separate project in the CI server ? It's what I begin to do at work. The advantage is to keep the integration build fast and we can have a look at the QA builds to improve them. Arnaud On Mon, Jul

Julia Antonova/Tumlare is out of office.

2008-07-20 Thread Julia Antonova
I will be out of the office starting 12.07.2008 and will not return until 28.07.2008. I will respond to your message when I return. In urgent cases please refer to Elena Tonoyan ([EMAIL PROTECTED]) or Daria Ignatieva ([EMAIL PROTECTED])

Re: [VOTE] Release maven-artifact-3.0-alpha-1

2008-07-20 Thread Brett Porter
Hi Oleg, Looking at the release, the signatures are from a generic key. While we're debating that in the other thread, for this release, can you sign the artifacts using your own key, and add that to the KEYS file in SVN? Also, the signatures do not need to be checksummed. Other than that

Re: Developing Maven 2.1

2008-07-20 Thread Wendy Smoak
On Sun, Jul 20, 2008 at 7:12 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > On 20-Jul-08, at 9:42 PM, Wendy Smoak wrote: > >> Yes. The svn commits need to show the person who actually made the >> change to svn. > > I can fix that, is that the only problem? No, but I think Brett has it covered. :)

Re: Developing Maven 2.1

2008-07-20 Thread Brett Porter
On 21/07/2008, at 12:20 PM, Jason van Zyl wrote: The important thing is that the release process does not use your credentials for either SVN or SSH when it's not you doing the release. I don't think that's important at all, but I can easily fix it. Do I have to SSH into your account o

Re: releasing the enforcer

2008-07-20 Thread Brett Porter
On 21/07/2008, at 12:23 PM, Brian E. Fox wrote: I confirmed my initial hunch but I'm not sure how to fix this the right way. Here's what is happening: The rule gets the list of plugins bound by the default lifecycles (additional lifecycles may be specified) and additional Plugins specifi

RE: releasing the enforcer

2008-07-20 Thread Brian E. Fox
I confirmed my initial hunch but I'm not sure how to fix this the right way. Here's what is happening: The rule gets the list of plugins bound by the default lifecycles (additional lifecycles may be specified) and additional Plugins specified by the user. It then gets the list of plugins specif

Re: How to validate a Maven release? Fwd: [VOTE] Release Maven antrun plugin version 1.2

2008-07-20 Thread Brett Porter
On 19/07/2008, at 11:26 PM, Dennis Lundberg wrote: I went and harvested the mojo-dev list for release vote comments, most of the from Benjamin. Some are specific to plugins, but many are general. Here's the list: Thanks Dennis! (and Benjamin :) Inherit from the latest released parent

Re: Developing Maven 2.1

2008-07-20 Thread Jason van Zyl
On 20-Jul-08, at 10:13 PM, Brett Porter wrote: On 18/07/2008, at 11:54 PM, Jason van Zyl wrote: I am actually trying to work with a developer who knows Hudson very well to create a better bridge from Maven and Hudson. Basically using Maven SCM (instead of the proliferation of Hudson plugi

Re: Developing Maven 2.1

2008-07-20 Thread Brett Porter
On 18/07/2008, at 11:54 PM, Jason van Zyl wrote: I am actually trying to work with a developer who knows Hudson very well to create a better bridge from Maven and Hudson. Basically using Maven SCM (instead of the proliferation of Hudson plugins doing exactly the same thing), creating a Ple

Re: Developing Maven 2.1

2008-07-20 Thread Jason van Zyl
On 20-Jul-08, at 9:42 PM, Wendy Smoak wrote: On Fri, Jul 18, 2008 at 6:00 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: They are not being shared. Hudson is running as a sand-boxed user where I have setup my credentials, so that the releases can be fully automated where the same set of a

Re: Developing Maven 2.1

2008-07-20 Thread Wendy Smoak
On Fri, Jul 18, 2008 at 6:00 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > They are not being shared. Hudson is running as a sand-boxed user where I > have setup my credentials, so that the releases can be fully automated where > the same set of attributes are used across the board. I tested my

Re: [mojo-dev] [jira] Created: (MOJO-1178) [plugin submission] versions-maven-plugin

2008-07-20 Thread Stephen Connolly
Well is anyone interested? If it's a blocker I can relicense it to the MIT license. I'm also working on two more goals: update-plugins try-updating-plugins On Fri, Jul 18, 2008 at 10:27 AM, Stephen Connolly (JIRA) <[EMAIL PROTECTED]> wrote: > [plugin submission] versions-maven-plugin > ---

Re: [VOTE] Release Maven antrun plugin version 1.2

2008-07-20 Thread Carlos Sanchez
Release was rolledback and performed again, site and staging repo updated, please restart the voting process http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&styleName=Html&version=12210 Staging repo: http://people.apache.org/~carlos/staging-repo Staging site: http://maven.apache

Re: How to validate a Maven release? Fwd: [VOTE] Release Maven antrun plugin version 1.2

2008-07-20 Thread Vincent Siveton
Hi, 2008/7/19, Jason van Zyl <[EMAIL PROTECTED]>: > This is great as long as it does not become bureaucratic and onerous for > everyone to do a release. Totally agree with you: it could be time consuming for the release manager and for the committers which review... > How to prevent that is cod