Re: Integration Testing

[John Casey]

my only recommendation would be to take a look at the maven-assembly-plugin
(SVN:
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin)
and go for something like that...

On 4/16/07, Barrie Treloar <[EMAIL PROTECTED]> wrote:


On 4/17/07, John Casey <[EMAIL PROTECTED]> wrote:
> Jerome, that link contains information on the strategy I've been using
in
> the assembly plugin, and it seems to work well (although it's a bit
slower,
> since it's spawning so many Maven builds). I'm hoping to converge the
tools
> we're using in the core ITs with those in the
maven-component-test-plugin
> (used to be maven-plugin-test-plugin), and the maven-invoker-plugin, and
> arrive at some single solution (a plugin) that we can use
everywhere...but I
> haven't even been able to come up with a unified feature list yet.

So, does anyone have a recommended approach so I can move forward in
the mean time?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Remove auto-resolution of plugin versions from Maven 2.1

[Barrie Treloar]

On 4/17/07, Kevin Menard <[EMAIL PROTECTED]> wrote:

support newer releases of external software.  At least in the case of
Selenium, the authors know that they're released version is broken and
their response is to just use SNAPSHOT.  That's the sort of scenario I'd
like to see avoided if possible.


That's not terribly helpful of the Selenium folks.

You should get more of their users to whinge.  Broken releases should
get fixed ASAP, or else dump Selenium and use something else.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Integration Testing

[Barrie Treloar]

On 4/17/07, John Casey <[EMAIL PROTECTED]> wrote:

Jerome, that link contains information on the strategy I've been using in
the assembly plugin, and it seems to work well (although it's a bit slower,
since it's spawning so many Maven builds). I'm hoping to converge the tools
we're using in the core ITs with those in the maven-component-test-plugin
(used to be maven-plugin-test-plugin), and the maven-invoker-plugin, and
arrive at some single solution (a plugin) that we can use everywhere...but I
haven't even been able to come up with a unified feature list yet.


So, does anyone have a recommended approach so I can move forward in
the mean time?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Integration Testing

[John Casey]

Jerome, that link contains information on the strategy I've been using in
the assembly plugin, and it seems to work well (although it's a bit slower,
since it's spawning so many Maven builds). I'm hoping to converge the tools
we're using in the core ITs with those in the maven-component-test-plugin
(used to be maven-plugin-test-plugin), and the maven-invoker-plugin, and
arrive at some single solution (a plugin) that we can use everywhere...but I
haven't even been able to come up with a unified feature list yet.

-john

On 4/15/07, Jerome Lacoste <[EMAIL PROTECTED]> wrote:


On 2/24/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> On 04/01/2007, at 4:32 PM, Brett Porter wrote:
>
> > Jason - any further thoughts on this?
>
> Ping... No is a valid answer :)
>
> I'd like to get your summary put somewhere individuals can pick
> things off to work on - probably a jira project for shared. WDYT?
>
> I'm overcommitted for working on things right now, but I know a
> couple of people are confused about the IT testing, and we've got all
> those chronically broken plugins. Volunteers?

I want to improve the state of IT for the mojos I work with (in
particular in the mojo project). I am particularly interested in doing
it in an sort of official/standard way.


- [ ] We need to standardize on integration testing in general. We
  have people going all over the place and it's a disaster.
- [ ] We have too many IT plugins (3)
- [ ] We have too many invokers (5)
- [ ] We have too many verifiers (3)

I've found this:
http://maven.apache.org/developers/committer-testing-plugins.html

Does that represent the current IT strategy 'standard' ? Was that
written after the point above was resolved ?

Cheers,

Jerome

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [vote] Release maven-developer-activity-plugin and maven-file-activity-plugin 1.6.1 for maven 1.X

[Dennis Lundberg]

+1

Arnaud HERITIER wrote:

Hi,

 Those two plugins have a similar fix and weren't release for several
months (more than 1 year in fact).

 Changes :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/changes-report.html#Release1_6_1-SNAPSHOT 

http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/changes-report.html#Release1_6_1-SNAPSHOT 



 


Staging sites :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/ 

http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/ 



 Download :

maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-developer-activity-plugin -Dversion=1.6.1-SNAPSHOT
maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-file-activity-plugin -Dversion=1.6.1-SNAPSHOT


+1 from me, 72h to vote

Cheers,




--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Remove auto-resolution of plugin versions from Maven 2.1

[Kevin Menard]

Apologies for the delayed response.  I must've missed the message.

I'd have to check with Andrus Adamchik, since he was the guy that had to
keep fixing the POM.  I know for certain that we've been bitten numerous
times by the Geronimo folk though, both transitively and directly.  We
also got bit by the whole surefire/classloader issue, which the
suggestions in this thread would take care of.

For my own stuff, I've had to rely on SNAPSHOT for Selenium and Cargo,
because either the released versions were broken in some way or didn't
support newer releases of external software.  At least in the case of
Selenium, the authors know that they're released version is broken and
their response is to just use SNAPSHOT.  That's the sort of scenario I'd
like to see avoided if possible.

-- 
Kevin 

> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, April 12, 2007 5:24 PM
> To: Maven Developers List
> Subject: Re: Remove auto-resolution of plugin versions from Maven 2.1
> 
> I'm interested to know which snapshots bit you guys so hard? 
> Was it a [set of] internal snapshots, or were they snapshots 
> from Maven or some other OSS project that you depend on or 
> use? If we start talking seriously about shorter dev cycles 
> and milestone releases with less of a barrier to release (for 
> alpha quality, for instance)...and start shunning snapshots 
> as an acceptable mechanism for distributing pre-release 
> code...would that have helped you all?
> 
> -john
> 
> On 4/12/07, Kevin Menard <[EMAIL PROTECTED]> wrote:
> >
> > I agree.  I am suggesting that it's a little too easy to 
> use SNAPSHOTs 
> > and that all that wonderful time maven was supposed to save you in 
> > preparing releases is trumped by the time it takes to just append 
> > -SNAPSHOT to a version number.  Sure, it's people abusing 
> it, but it's 
> > easy to abuse and looks like it's officially condoned as proper 
> > behavior.  Things get even murkier when transitive dependencies are 
> > considered.  So, I'm not suggesting dumping SNAPSHOT wholesale, but 
> > making it more difficult to distribute an artifact via 
> SNAPSHOT (maybe 
> > require the end user to have to agree to use a new SNAPSHOT 
> each time 
> > one is available or something).
> >
> > Maybe we'll just have to agree to disagree.  I will say that this 
> > matter has bitten the Cayenne team a few times now, and we've come 
> > close to dumping maven altogether.  It got to the point 
> where we had 
> > to start pinning SNAPSHOTs by timestamp via a guess and 
> check method.  
> > Perhaps the plugin Nigel suggested would help matters, though.
> >
> > --
> > Kevin
> >
> > > -Original Message-
> > > From: Brian E. Fox [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, April 12, 2007 3:10 PM
> > > To: Maven Developers List
> > > Subject: RE: Remove auto-resolution of plugin versions from Maven 
> > > 2.1
> > >
> > >  Snapshots are a very good thing for internal 
> development. It would 
> > > be impossible to manage my builds without them. I think 
> that people 
> > > using snapshots of plugins are a symptom of another 
> problem -- long 
> > > release cycles. Just because people do bad things with snapshots 
> > > doesn't mean snapshots should go away.
> > >
> > > It already takes a little effort to get at them, the 
> snapshot repo 
> > > isn't part of the super-pom, so if you go out of your way to get 
> > > them, you should understand the consequences. It's like 
> me picking 
> > > up an unstable version of some jar and then complaining that it 
> > > broke later and asking the creators to stop releasing unstable 
> > > versions at all(that are clearly marked as such). People 
> would then 
> > > just go get the code anyway.
> > >
> > > -Original Message-
> > > From: Kevin Menard [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, April 12, 2007 1:09 PM
> > > To: Maven Developers List
> > > Subject: RE: Remove auto-resolution of plugin versions from Maven 
> > > 2.1
> > >
> > > Right.
> > >
> > > My point is that regardless of what the original 
> intention may have 
> > > been, the current process facilitates laziness via SNAPSHOTs.  
> > > Without them, incremental builds would be necessary, which would 
> > > give fixed version numbers with known binaries.
> > >
> > > If the plan is to take actions to help prevent users from having 
> > > things break on them, this may be easier than the path 
> you outlined.
> > >
> > > --
> > > Kevin
> > >
> > > >
> > >
> > > 
> 
> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > > additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 

-
To unsubscribe, e-mail

Re: [vote] release maven-release-1 parent and maven-release-manager-1.0-alpha-1

[Jesse McConnell]

Summary: 6 binding +1 (jesse, emmanuel, jdcasey, snicoll, arnaud, vsiveton)

I'll get this moved over and synced out today.

thanks!

next up, continuum 1.1 alpha 1

On 4/15/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:

On 4/15/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
> Stephane Nicoll wrote:
> > On 4/14/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
> >>
> >> Too late for this release, but could someone take a look at MRELEASE-137
> >> so it gets into the next one? It's a trivial one-liner fix. The attached
> >> patch is for maven-release-plugin, but the relevant class has since
> >> moved into maven-release-manager. It's obvious how to forward port the
> >> single change to the new code.
> >>
> > The change does not seem that trivial to me. A potential
> > IndexOutOfBoundsException might be trhown. Jason is the assignee but
> > i'll try to have a look.
>
> The current code calls:
>
> list.get( 0 )
>
> the fix is to change that to:
>
> list.get( list.size() - 1 )
>
> Surely the only way the second one could cause an IOOBE is if the list
> is empty, in which case the current code would also IOOBE?
>
I'm missing coffee. Forget it :)



> Max.
>
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
jesse mcconnell
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Clover plugin v2.4 - Take 2

[Andrew Williams]

+1
On 15 Apr 2007, at 19:55, Vincent Massol wrote:


Hi,

As Mike Perham pointed out the Clover license for the release  
clover plugin (ie v2.3) has expired. Thus the urgency to release  
version 2.4.


Here's the release notes for 2.4:

** Bug
* [MCLOVER-45] - Excluded files should be added to compiled  
sources
* [MCLOVER-53] - Clover plugin installs clover instrumented  
source in local repository
* [MCLOVER-66] - The report goal doesn't support a user- 
provided Clover license
* [MCLOVER-68] - XDoclet plugin executes before the Clover  
plugin in the lifecycle forked by the latter


** Improvement
* [MCLOVER-38] - Allow check Mojo to be overriden by a  
failOnViolation parameter in the same way PMD and Checkstyle can

* [MCLOVER-65] - Clover license has expired

** Task
* [MCLOVER-67] - Remove deprecated licenseFile configuration  
parameter


The plugin is staged at http://people.apache.org/~vmassol/maven- 
staging/


Here's my +1

Thanks
-Vincent




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT][VOTE] maven-remote-resources-plugin 1.0-alpha-5

[Daniel Kulp]

5  +1 binding votes (Jason van Zyl,  John Casey,  Emmanuel Venisse, 
Joakim Erdfelt, Vincent Siveton)
3 +1 non-binding votes (Jason Dillon, Andrew Williams, Daniel Kulp)
No -1 votes or new issues raised.

This vote passes.   

Dan



On Thursday 12 April 2007 13:13, Daniel Kulp wrote:
> I'd like to release version 1.0-alpha-5 of the
> maven-remote-resources-plugin.   This resolves one critical bug, but
> also adds some new features to make it a bit more usable.
>
>
> Release Notes - Maven 2.x Remote Resources Plugin - Version
> 1.0-alpha-5
>
> ** Bug
> * [MRRESOURCES-18] - Error when no 'inceptionYear' is specified in
> POM
>
> ** Improvement
> * [MRRESOURCES-19] - Bundle mojo only looks for txt and vm files
> * [MRRESOURCES-20] - Support for binary resources
> * [MRRESOURCES-21] - Supplement the data model used by Velocity
>
>
> Staging area:
> http://people.apache.org/~dkulp/stage_remoteresources/
>
> Tag:
> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-remote-resour
>ces-plugin-1.0-alpha-5/

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Clover plugin v2.4 - Take 2

[Mike Perham]

+1

On 4/15/07, Vincent Massol <[EMAIL PROTECTED]> wrote:

Hi,

As Mike Perham pointed out the Clover license for the release clover
plugin (ie v2.3) has expired. Thus the urgency to release version 2.4.

Here's the release notes for 2.4:

** Bug
 * [MCLOVER-45] - Excluded files should be added to compiled sources
 * [MCLOVER-53] - Clover plugin installs clover instrumented
source in local repository
 * [MCLOVER-66] - The report goal doesn't support a user-provided
Clover license
 * [MCLOVER-68] - XDoclet plugin executes before the Clover
plugin in the lifecycle forked by the latter

** Improvement
 * [MCLOVER-38] - Allow check Mojo to be overriden by a
failOnViolation parameter in the same way PMD and Checkstyle can
 * [MCLOVER-65] - Clover license has expired

** Task
 * [MCLOVER-67] - Remove deprecated licenseFile configuration
parameter

The plugin is staged at http://people.apache.org/~vmassol/maven-staging/

Here's my +1

Thanks
-Vincent




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Clover plugin v2.4 - Take 2

[John Casey]

+I

On 4/16/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote:


+1

Vincent Massol wrote:
> Hi,
>
> As Mike Perham pointed out the Clover license for the release clover
> plugin (ie v2.3) has expired. Thus the urgency to release version 2.4.
>
> Here's the release notes for 2.4:
>
> ** Bug
> * [MCLOVER-45] - Excluded files should be added to compiled sources
> * [MCLOVER-53] - Clover plugin installs clover instrumented source in
> local repository
> * [MCLOVER-66] - The report goal doesn't support a user-provided
> Clover license
> * [MCLOVER-68] - XDoclet plugin executes before the Clover plugin in
> the lifecycle forked by the latter
>
> ** Improvement
> * [MCLOVER-38] - Allow check Mojo to be overriden by a failOnViolation
> parameter in the same way PMD and Checkstyle can
> * [MCLOVER-65] - Clover license has expired
>
> ** Task
> * [MCLOVER-67] - Remove deprecated licenseFile configuration parameter
>
> The plugin is staged at http://people.apache.org/~vmassol/maven-staging/
>
> Here's my +1
>
> Thanks
> -Vincent
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> !DSPAM:602,46227532110829182317745!
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [vote] Release maven-site-plugin 1.7.2 for maven 1.X

[Stephane Nicoll]

+1

Stéphane

On 4/16/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:

Hi,

  I encountered some problems with the site plugin and its rsync deployment
feature.
  I propose to release a new version to fix these problems.

  Changes :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT
  Staging site :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/
  Download :
  maven plugin:download
-Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,
http://repo1.maven.org/maven
-DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.7.2-SNAPSHOT

+1 from me, 72h to vote

Cheers,
Arnaud



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [vote] Release maven-announcement-plugin 1.4.1 for maven 1.X

[Stephane Nicoll]

+1

Stéphane

On 4/16/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:

Hi,

  In the logic to try to release often I propose to release the announcement
which has only one minor change. It's to have these one included in the RC1.

  Changes :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/changes-report.html#Release1_4_1-SNAPSHOT


Staging site :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/

  Download :

maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-site-plugin -Dversion=1.4.1-SNAPSHOT

+1 from me, 72h to vote

Cheers,



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [vote] Release maven-developer-activity-plugin and maven-file-activity-plugin 1.6.1 for maven 1.X

[Lukas Theussl]

+1

-Lukas

Arnaud HERITIER wrote:

Hi,

 Those two plugins have a similar fix and weren't release for several
months (more than 1 year in fact).

 Changes :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/changes-report.html#Release1_6_1-SNAPSHOT 

http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/changes-report.html#Release1_6_1-SNAPSHOT 



 


Staging sites :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/ 

http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/ 



 Download :

maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-developer-activity-plugin -Dversion=1.6.1-SNAPSHOT
maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-file-activity-plugin -Dversion=1.6.1-SNAPSHOT


+1 from me, 72h to vote

Cheers,



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [vote] Release maven-announcement-plugin 1.4.1 for maven 1.X

[Lukas Theussl]

+1

-Lukas

Arnaud HERITIER wrote:

Hi,

 In the logic to try to release often I propose to release the announcement
which has only one minor change. It's to have these one included in the 
RC1.


 Changes :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/changes-report.html#Release1_4_1-SNAPSHOT 



 


Staging site :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/ 



 Download :

maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-site-plugin -Dversion=1.4.1-SNAPSHOT

+1 from me, 72h to vote

Cheers,



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [vote] Release maven-site-plugin 1.7.2 for maven 1.X

[Lukas Theussl]

+1

-Lukas

Arnaud HERITIER wrote:

Hi,

 I encountered some problems with the site plugin and its rsync deployment
feature.
 I propose to release a new version to fix these problems.

 Changes :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT 


 Staging site :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ 


 Download :
 maven plugin:download
-Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,
http://repo1.maven.org/maven
-DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.7.2-SNAPSHOT

+1 from me, 72h to vote

Cheers,
Arnaud



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [vote] Release maven-developer-activity-plugin and maven-file-activity-plugin 1.6.1 for maven 1.X

[Stephane Nicoll]

+1

Stéphane

On 4/16/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:

Hi,

  Those two plugins have a similar fix and weren't release for several
months (more than 1 year in fact).

  Changes :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/changes-report.html#Release1_6_1-SNAPSHOT
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/changes-report.html#Release1_6_1-SNAPSHOT


Staging sites :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/

  Download :

maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-developer-activity-plugin -Dversion=1.6.1-SNAPSHOT
maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1
-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven
-DartifactId=maven-file-activity-plugin -Dversion=1.6.1-SNAPSHOT


+1 from me, 72h to vote

Cheers,



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]