Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Dan Fabulich
(ahem) It looks like I forgot to check in my PMC Member status. :-) https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=587312&r2=629352&diff_format=h Also, uh, Surefire 2.4.2 would be cool. [2.4.1 has that @aggregator bug that Javadoc has, I'm sure we'd all hate that. ;-)] -Dan

site:stage-deploy asks for a password?

2008-02-19 Thread Dan Fabulich
The updated version of the release process says to do a site:stage-deploy after doing a site:deploy, to create a versioned staged website. I'd never done that before; when I tried just now, I was prompted for a password. [INFO] Generate "Project Team" report. Using private key: C:\Docum

Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1

2008-02-19 Thread Dan Fabulich
+1. I just used it to stage Surefire 2.4.2; looks good to me. -Dan Wendy Smoak wrote: I'd like to do the first release of the Maven Stage Plugin. This plugin is already being used for Maven releases, and although it has limited functionality, it seems to be stable. There are four open issue

[RESULT] [VOTE] Release Maven Surefire version 2.4.2

2008-02-19 Thread Dan Fabulich
Vote passed. +1 binding: Dan Fabulich, Arnaud Heritier, Wendy Smoak, Brett Porter +1 non-binding: Sejal Patel, Fabrice Bellingard I'll try and stage this now. [This will be a great opportunity to try the new Stage plugin... ;-)] -Dan -- Forwarded message -- Date: Fri, 15 Fe

Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1

2008-02-19 Thread Wendy Smoak
On Feb 19, 2008 1:01 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > The -sources jar is missing LICENSE and NOTICE files. I dislike changing anything after a vote has started. If it had been the main artifact I would definitely have started over with the release and vote. However, this time I

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Brett Porter
I was sitting in the plexus-digester directory and ran: mvn deploy -DaltDeploymentRepository=id::default::file://localhost/Users/brett/Desktop/snapshots On 20/02/2008, at 11:03 AM, John Casey wrote: Can you tell me what you tried? It should work with both the -D parameter and with the proper

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread John Casey
Removed in revId: 629280 https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml? r1=587312&r2=629280&diff_format=h On Feb 19, 2008, at 5:56 PM, Vincent Siveton wrote: Hi, Also, I would like to remove since it is not a Maven TLP jira. WDYT? Anyway, I'm +1 and thanks for this Dennis!

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread John Casey
Can you tell me what you tried? It should work with both the -D parameter and with the property that I tried...my attempt doesn't work, but yours does, apparently? In any case, this modification doesn't make any difference if the deploy plugin is fixed, but in the meantime will enable this

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread John Casey
Ah, it's already in the maven pom.xml... -john On Feb 19, 2008, at 5:56 PM, Vincent Siveton wrote: Hi, Also, I would like to remove since it is not a Maven TLP jira. WDYT? Anyway, I'm +1 and thanks for this Dennis! Cheers, Vincent 2008/2/19, Dennis Lundberg <[EMAIL PROTECTED]>: Hi To g

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread John Casey
+1 to the removal of issueManagement. I can add that back into the maven pom.xml. -john On Feb 19, 2008, at 5:56 PM, Vincent Siveton wrote: Hi, Also, I would like to remove since it is not a Maven TLP jira. WDYT? Anyway, I'm +1 and thanks for this Dennis! Cheers, Vincent 2008/2/19, Den

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread John Casey
That only affects the release repository. You can test it with this: http://www.commonjava.org/~jdcasey/code/java/maven/examples/deploy- test.tar.gz When you open that sample project, you'll need to run: mvn -s ./settings.xml deploy If the normal override is working, it should deploy to /tmp

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Brett Porter
I just tried it and it seems to work for everything except updating the build number - probably because it retrieves it from somewhere other than the deployment repo. Probably a bug in the deploy plugin that should be fixed instead? - Brett On 20/02/2008, at 10:10 AM, Brian E. Fox wrote:

RE: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Brian E. Fox
It doesn't work for snapshots iirc. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 19, 2008 5:53 PM To: Maven Developers List Subject: Re: [VOTE] Release maven-parent pom 8 What's wrong with the altDeploymentRepository setting of the deploy plug

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Jason van Zyl
On 19-Feb-08, at 2:56 PM, Vincent Siveton wrote: Hi, Also, I would like to remove since it is not a Maven TLP jira. WDYT? +1 Each individual project should have their own. Anyway, I'm +1 and thanks for this Dennis! Cheers, Vincent 2008/2/19, Dennis Lundberg <[EMAIL PROTECTED]>: Hi

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Vincent Siveton
Hi, Also, I would like to remove since it is not a Maven TLP jira. WDYT? Anyway, I'm +1 and thanks for this Dennis! Cheers, Vincent 2008/2/19, Dennis Lundberg <[EMAIL PROTECTED]>: > Hi > > To get the latest version of maven-source-plugin into our toolchain, I'd > like to release maven parent

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Brett Porter
What's wrong with the altDeploymentRepository setting of the deploy plugin? On 20/02/2008, at 9:31 AM, John Casey wrote: I'd like to add a small change to the parent pom to allow override of the snapshot repository in the distribution management section via profile property, so we can run

RE: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Brian E. Fox
+1 to the change and subsequent release -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 19, 2008 5:31 PM To: Maven Developers List Subject: Re: [VOTE] Release maven-parent pom 8 I'd like to add a small change to the parent pom to allow override of

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread John Casey
The revId on that is: 629256 So, the URL I'd propose we use is: https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml? r1=587312&r2= 629256&diff_format=h Thanks, -john On Feb 19, 2008, at 5:31 PM, John Casey wrote: I'd like to add a small change to the parent pom to allow override

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread John Casey
I'd like to add a small change to the parent pom to allow override of the snapshot repository in the distribution management section via profile property, so we can run CI builds on a closed system without the need of people.apache.org. I can get that in tonight, but after that I'm +1. -jo

RE: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Brian E. Fox
The only problem is if someone figured out a workaround by specifying in depMgt specifically to override the plugin rev. We should fix this + the ability to override a plugin's dependency version in the same release so people at least have an option. -Original Message- From: [EMAIL PROTECT

Re: [VOTE] Release maven-parent pom 8

2008-02-19 Thread Olivier Lamy
Hi, Is there a reason to not upgrade jar plugin to 2.2 and surefire plugin to 2.4.1 ? -- Olivier 2008/2/19, Dennis Lundberg <[EMAIL PROTECTED]>: > Hi > > To get the latest version of maven-source-plugin into our toolchain, I'd > like to release maven parent pom r628845 as version 8. > > Source: >

Re: [vote] Take-2 release maven-archetype-plugin-2.0-alpha-2

2008-02-19 Thread Raphaël Piéroni
+1 Tested to generate/create-from-project on both linux+jdk6+mvn2.0.08 an windows +jdk4+mvn2.0.8 Regards, Raphaël 2008/2/19, Brian E. Fox <[EMAIL PROTECTED]>: > Rerolled to correct the tag and 2 header issues identified by Brett. > > > > The most important early issues have been fixed and we nee

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Carlos Sanchez
I dont think is related, this bug only affects plugins that use dependencyManagement. It does nothing with the plugin dependencies. This wold change plugin classpath for all those plugins that have dependency management, but it will change them to what the plugin was successfully built with, so I

[VOTE] Release maven-parent pom 8

2008-02-19 Thread Dennis Lundberg
Hi To get the latest version of maven-source-plugin into our toolchain, I'd like to release maven parent pom r628845 as version 8. Source: https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=587312&r2=628845&diff_format=h The vote will be open for 72 hours. +1 from me -- Dennis

Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1

2008-02-19 Thread Dennis Lundberg
maven-stage-plugin --> maven-plugins-10 --> maven-parent-7, which uses maven-source-plugin-2.0.3 which had a bug: http://jira.codehaus.org/browse/MSOURCES-26 That's the main reason why I want to push out new releases of the parent POMs. Jason van Zyl wrote: How is the release toolchain not

Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1

2008-02-19 Thread Jason van Zyl
How is the release toolchain not doing that? Wendy, did you use the release plugin? On 19-Feb-08, at 12:01 PM, Dennis Lundberg wrote: The -sources jar is missing LICENSE and NOTICE files. To solve it either add a build plugin in the pom for maven-sources- plugin-2.0.4 (see below) or wait unt

Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1

2008-02-19 Thread Dennis Lundberg
The -sources jar is missing LICENSE and NOTICE files. To solve it either add a build plugin in the pom for maven-sources-plugin-2.0.4 (see below) or wait until the parent poms are released. org.apache.maven.plugins maven-source-plugin 2.0.4 Apart from th

Re: svn commit: r628845 - /maven/pom/trunk/maven/pom.xml

2008-02-19 Thread Dennis Lundberg
Wendy Smoak wrote: On Feb 18, 2008 4:12 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hi Wendy Did you mean for this to go into Maven parent pom? The URL in your change suggests to me that is intended for Maven components pom. If left in Maven parent pom there will be URL clashes between say

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Jason van Zyl
On 19-Feb-08, at 9:56 AM, Niall Pemberton wrote: On Feb 19, 2008 5:46 PM, Carlos Sanchez <[EMAIL PROTECTED]> wrote: On Feb 19, 2008 9:40 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 19-Feb-08, at 9:36 AM, Carlos Sanchez wrote: I think you misunderstood. The dependencyManagement is used

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Niall Pemberton
On Feb 19, 2008 5:46 PM, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > On Feb 19, 2008 9:40 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > > On 19-Feb-08, at 9:36 AM, Carlos Sanchez wrote: > > > > > I think you misunderstood. The dependencyManagement is used for > > > project dependencies, fine w

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Jason van Zyl
On 19-Feb-08, at 9:46 AM, Carlos Sanchez wrote: On Feb 19, 2008 9:40 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 19-Feb-08, at 9:36 AM, Carlos Sanchez wrote: I think you misunderstood. The dependencyManagement is used for project dependencies, fine with that. When you use a plugin no de

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Carlos Sanchez
On Feb 19, 2008 9:40 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 19-Feb-08, at 9:36 AM, Carlos Sanchez wrote: > > > I think you misunderstood. The dependencyManagement is used for > > project dependencies, fine with that. > > When you use a plugin no dependencyManagement is applied. The cur

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Jason van Zyl
On 19-Feb-08, at 9:36 AM, Carlos Sanchez wrote: I think you misunderstood. The dependencyManagement is used for project dependencies, fine with that. When you use a plugin no dependencyManagement is applied. The current project depMan shouldn't be applied because it's only for projects, so that

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Carlos Sanchez
I think you misunderstood. The dependencyManagement is used for project dependencies, fine with that. When you use a plugin no dependencyManagement is applied. The current project depMan shouldn't be applied because it's only for projects, so that's ok. The problem comes when a plugin is built usi

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Jason van Zyl
On 19-Feb-08, at 9:07 AM, Carlos Sanchez wrote: On Feb 19, 2008 7:46 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 18-Feb-08, at 11:54 PM, Carlos Sanchez wrote: I'd like to get some feedback in MNG-3410, particularly from John as he has been working on this. If you build and install a pl

Re: atypical plugin use cases

2008-02-19 Thread Brett Porter
On 19/02/2008, at 9:50 PM, Stephen Connolly wrote: My rule of thumb is to _always_ run the tests twice, once with coverage and once without. The test failure during the second (instrumented) execution should not fail the build. Yes, this is the recommendation I always make too, to ensure

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Carlos Sanchez
On Feb 19, 2008 7:46 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 18-Feb-08, at 11:54 PM, Carlos Sanchez wrote: > > > I'd like to get some feedback in MNG-3410, particularly from John as > > he has been working on this. > > > > If you build and install a plugin with managed versions that aff

Re: RBAC vs JASS/Roles (was: Re: Plan to migrate towards Spring?)

2008-02-19 Thread Brett Porter
On 20/02/2008, at 1:36 AM, Joakim Erdfelt wrote: nicolas de loof wrote: "Integrate RedBack / Spring into Archiva." What is the advantage of redback compared to spring-security (aka "acegi") ? spring-security allready supports role-based secutiry, DB user store and "remember me". Nico.

Re: [MNG-3410] Plugin managed versions are ignored

2008-02-19 Thread Jason van Zyl
On 18-Feb-08, at 11:54 PM, Carlos Sanchez wrote: I'd like to get some feedback in MNG-3410, particularly from John as he has been working on this. If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ign

Re: [vote] Benjamin Bentmann as Maven committer

2008-02-19 Thread Andrew Williams
+1 Andy On 18 Feb 2008, at 17:38, Lukas Theussl wrote: I'd like to propose giving commit access to Benjamin. During the last few months, he has provided patches in so many areas of Maven that I can't list them all here (various plugins, surefire, doxia,...), including documentation and t

RE: Maven Filtering component

2008-02-19 Thread Brian E. Fox
I also know that in terms of pom specified property files, it's last wins currently. -Original Message- From: Stephane Nicoll [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 19, 2008 5:37 AM To: Maven Developers List Subject: Re: Maven Filtering component I guess we should have a loo

Re: [vote] Benjamin Bentmann as Maven committer

2008-02-19 Thread Mauro Talevi
+1 Lukas Theussl wrote: I'd like to propose giving commit access to Benjamin. During the last few months, he has provided patches in so many areas of Maven that I can't list them all here (various plugins, surefire, doxia,...), including documentation and translations, and he has not been a

Re: Maven Filtering component

2008-02-19 Thread Olivier Lamy
Yep sure. Currently, the new component use the same strategy as the maven-resources-plugin. -- Olivier 2008/2/19, Stephane Nicoll <[EMAIL PROTECTED]>: > I guess we should have a look to the way this is done currently to > avoid breaking the backward compat. > > On Feb 19, 2008 11:30 AM, Olivier L

Re: atypical plugin use cases

2008-02-19 Thread Stephen Connolly
On Feb 18, 2008 8:03 PM, Brett Porter <[EMAIL PROTECTED]> wrote: > On 19/02/2008, at 3:15 AM, John Casey wrote: > Things like: > - running the tests twice by necessity Having being burned by this little foible... I often see people complain that the code coverage tools runs the unit tests twice

Re: Maven Filtering component

2008-02-19 Thread Stephane Nicoll
I guess we should have a look to the way this is done currently to avoid breaking the backward compat. On Feb 19, 2008 11:30 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote: > Sure, could be better. > But we have to agree on the order : > * System Properties > * pom.properties > * List of properties (

Re: Maven Filtering component

2008-02-19 Thread Olivier Lamy
Sure, could be better. But we have to agree on the order : * System Properties * pom.properties * List of properties ( the method has a parameter which accept a List of String -> path properties files ) (war plugin use it to pass a list of properties file). * pom.filters * pom.build.filters ? --

Re: Maven Filtering component

2008-02-19 Thread Stephane Nicoll
This one was very much expected, thanks for doing this. However, I think that we should use a first-win strategy, otherwise there is no way to control the actual value of a property. First-win strategy is mainly used everywhere in the war plugin and ease a lot of stuff Is there any reason you cho

Maven Filtering component

2008-02-19 Thread Olivier Lamy
Hi, As you know some plugins made some filtering base on the code coming from the maven-resources-plugin. This means there are some copy and paste from the resources plugin source to other plugins. To prevent this, the code from the resources plugin has been put in a plexus component (currently in

SCM-355

2008-02-19 Thread Siarhei Dudzin
Hi All, Any chance someone could have a look at SCM-355? There is patch including documentation available... Siarhei

Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1

2008-02-19 Thread Olivier Lamy
+1. -- Olivier 2008/2/19, Jason van Zyl <[EMAIL PROTECTED]>: > +1 > > On 18-Feb-08, at 8:58 PM, Wendy Smoak wrote: > > > I'd like to do the first release of the Maven Stage Plugin. This > > plugin is already being used for Maven releases, and although it has > > limited functionality, it seems t