You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2007/04/03 04:31:41 UTC
RE: maven-enforcer-plugin
Ok, a little more refactoring. The Custom rules can now get to the
ExpressionEvaluator so they can get pretty much anything a plugin could
get. The sites are updated to contain info about the standard rules and
the custom rule creation:
http://maven.apache.org/plugins/maven-enforcer-plugin/
http://maven.apache.org/shared/maven-enforcer-rule-api/index.html
I'll let this linger for a day or so and then call a vote if nothing
turns up.
Thanks,
Brian
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Thursday, March 29, 2007 11:59 PM
To: Maven Developers List
Subject: RE: maven-enforcer-plugin
I reimplemented the enforcer plugin along the lines of Jason D's idea[1]
and I think this is a much more extensible solution. The rules now
implement a common interface in shared/maven-enforcer-rule-api and users
will be able to inject their own custom rules. By defining the interface
external to the plugin, the Lint idea that JVZ put out[2] should be able
to invoke these rules, as will IDEs.
Please take a look at the site to see how the plugin works and provide
any suggestions. I still need to document how to create your own rules
and inject them, but I believe everything else is covered. A snapshot of
1.0-alpha-1 has also been deployed for testing. (I believe Geronimo is
already using it)
http://maven.apache.org/plugins/maven-enforcer-plugin (just deployed,
may take a while to refresh)
[1]
http://www.nabble.com/maven-enforcer-plugin-tf3431452s177.html#a9565974
[2] http://www.nabble.com/Maven-Lint-tf3462956s177.html#a9661545
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Tuesday, March 20, 2007 12:05 AM
To: Maven Developers List
Subject: maven-enforcer-plugin
There is a new plugin that I'd like to get some feedback on,
particularly on non-windows os's and the unit tests.
The maven-enforcer-plugin picks up where <prerequisites> leaves off and
allows control over the maven, jdk and os versions of a build.
This plugin was initially conceived here:
http://www.nabble.com/Control-of-maven-using-prerequisites-tf3231437s177
.html#a8979318
And here:
http://www.nabble.com/Why-is-prerequisites-not-inherited--tf3236197s177.
html#a9016296
1.0-alpha-1-SNAPSHOT is deployed and the site is here:
http://maven.apache.org/plugins/maven-enforcer-plugin/ (just deployed so
give it a little bit to completely update)
If all goes well and no major issues are uncovered, then I think it's
ready for staging and a vote.
Thanks,
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: maven-enforcer-plugin
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>More explicitly:
>[INFO] Used undeclared dependencies:
>[WARNING] None
Ah, that's the dependency plugin. Yes I already fixed that but not
before it was staged and a vote called.
> I confused verify with validate so I'll change that. I thought you
could
> bind it to another phase if you want, but if you don't specify one, it
> will go with the mojo default?
>Perhaps, I have not yet tried...
I just double checked that you can override it. I'm not able to get the
plugin to work with validate or initialize, I'm not sure why. There
doesn't appear to be a common lifecycle between default and site, so
there's now way I can bind it to both by default, but a user could.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-enforcer-plugin
Posted by Jerome Lacoste <je...@gmail.com>.
On 4/3/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> >some more feedback:
> >* Is that useful ?
> >[WARNING] None
>
> I'll remove that, not sure where it's from.
More explicitly:
[INFO] Used undeclared dependencies:
[WARNING] None
> >* enforce-one mojo attached to verify phase. I would have preferred
> >the build to fail as early as possible if it is to tell me that I am
> >using the wrong JDK/maven version... Shouldn't we let the user decide
> >of the phase to attach the mojo to ?
>
> I confused verify with validate so I'll change that. I thought you could
> bind it to another phase if you want, but if you don't specify one, it
> will go with the mojo default?
Perhaps, I have not yet tried...
J
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: maven-enforcer-plugin
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>some more feedback:
>* Is that useful ?
>[WARNING] None
I'll remove that, not sure where it's from.
>* enforce-one mojo attached to verify phase. I would have preferred
>the build to fail as early as possible if it is to tell me that I am
>using the wrong JDK/maven version... Shouldn't we let the user decide
>of the phase to attach the mojo to ?
I confused verify with validate so I'll change that. I thought you could
bind it to another phase if you want, but if you don't specify one, it
will go with the mojo default?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-enforcer-plugin
Posted by Jerome Lacoste <je...@gmail.com>.
On 4/3/07, Jerome Lacoste <je...@gmail.com> wrote:
> On 4/3/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Ok, a little more refactoring. The Custom rules can now get to the
> > ExpressionEvaluator so they can get pretty much anything a plugin could
> > get. The sites are updated to contain info about the standard rules and
> > the custom rule creation:
> > http://maven.apache.org/plugins/maven-enforcer-plugin/
> > http://maven.apache.org/shared/maven-enforcer-rule-api/index.html
> >
> > I'll let this linger for a day or so and then call a vote if nothing
> > turns up.
>
> - typo in the usage.html
>
> </requireMavenVesion> -> </requireMavenVersion>
some more feedback:
* Is that useful ?
[WARNING] None
* enforce-one mojo attached to verify phase. I would have preferred
the build to fail as early as possible if it is to tell me that I am
using the wrong JDK/maven version... Shouldn't we let the user decide
of the phase to attach the mojo to ?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-enforcer-plugin
Posted by Jerome Lacoste <je...@gmail.com>.
On 4/3/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Ok, a little more refactoring. The Custom rules can now get to the
> ExpressionEvaluator so they can get pretty much anything a plugin could
> get. The sites are updated to contain info about the standard rules and
> the custom rule creation:
> http://maven.apache.org/plugins/maven-enforcer-plugin/
> http://maven.apache.org/shared/maven-enforcer-rule-api/index.html
>
> I'll let this linger for a day or so and then call a vote if nothing
> turns up.
- typo in the usage.html
</requireMavenVesion> -> </requireMavenVersion>
- would there be a way to make sure the enforcer runs for every maven
invocation, not just in the default lifecycle ? E.g. mvn site doesn't
trigger the check.
- finally do we want to provide a report?
-- if so, we perhaps need to add a mechanism to allow the rule
information to be displayed (visitor pattern for the rule? description
in a particular place ? Auto-generated information ?)
-- would there be a way to make this report part of the project
information (not a 'usual' report)?
J
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: maven-enforcer-plugin
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Ok I understand now. Lets punt alpha-1 and then we can play around with
various options to get this information. It will probably represent an
addition to the rule interface so it won't be intrusive (and if it is,
well it's alpha-1 ;-) )
-----Original Message-----
From: Jerome Lacoste [mailto:jerome.lacoste@gmail.com]
Sent: Tuesday, April 03, 2007 7:05 PM
To: Maven Developers List
Subject: Re: maven-enforcer-plugin
On 4/3/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > The Require OS Version rules docs is using <goal>os</goal> instead
of
>
> ><goal>require</goal> (or <goal>require-once</goal>).
>
> Good catch. I'll make that change.
>
> > Is it close to time for a release of 1.0-alpha-1 of this puppy yet?
>
> Getting there. I want to explore Jerome's comments about reports and a
> vistor pattern. I haven't spent a lot of time thinking about it, but
I'm
> not sure how a visitor would help here. We really are only interested
in
> the message coming back. A report mojo could catch all the rule
results
> and report them. Comments? What am I missing?
Don't block the release of alpha-1 for that.
I wanted to have a report that says: this project requires maven 2.0.6
and SDK 1.5 without having to look at the pom.
Why a Visitor? Because you can specify your rule implementation, and
that might represent a complex rule, so I thought that only the rule
would be able to know about its configuration and the meaning of the
values. I don't like the idea in particular but that was the first one
that came to my head.
Another idea is to just publish the XML fragment for the plugin
configuration with each node linked to the rule APIs for further
documentation. That should be sufficient and simpler...
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-enforcer-plugin
Posted by Jerome Lacoste <je...@gmail.com>.
On 4/3/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > The Require OS Version rules docs is using <goal>os</goal> instead of
>
> ><goal>require</goal> (or <goal>require-once</goal>).
>
> Good catch. I'll make that change.
>
> > Is it close to time for a release of 1.0-alpha-1 of this puppy yet?
>
> Getting there. I want to explore Jerome's comments about reports and a
> vistor pattern. I haven't spent a lot of time thinking about it, but I'm
> not sure how a visitor would help here. We really are only interested in
> the message coming back. A report mojo could catch all the rule results
> and report them. Comments? What am I missing?
Don't block the release of alpha-1 for that.
I wanted to have a report that says: this project requires maven 2.0.6
and SDK 1.5 without having to look at the pom.
Why a Visitor? Because you can specify your rule implementation, and
that might represent a complex rule, so I thought that only the rule
would be able to know about its configuration and the meaning of the
values. I don't like the idea in particular but that was the first one
that came to my head.
Another idea is to just publish the XML fragment for the plugin
configuration with each node linked to the rule APIs for further
documentation. That should be sufficient and simpler...
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-enforcer-plugin
Posted by Jason Dillon <ja...@planet57.com>.
On Apr 3, 2007, at 1:24 PM, Brian E. Fox wrote:
>> Is it close to time for a release of 1.0-alpha-1 of this puppy yet?
>
> Getting there. I want to explore Jerome's comments about reports and a
> vistor pattern. I haven't spent a lot of time thinking about it,
> but I'm
> not sure how a visitor would help here. We really are only
> interested in
> the message coming back. A report mojo could catch all the rule
> results
> and report them. Comments? What am I missing?
>
> I don't want to do a release until we can be relatively sure the
> interface for the rules won't change.
This is an 1.0-alpha-1 release... I don't see any harm in making one
right now, and then if needed an alpha-2 if something internal
changes dramatically.
I would like to use this plugin for all of the Geronimo builds... but
a few are going to be coming up for release soon, and well, until
there is a release of this I can't really use it for those projects.
I would like to see 1.0-alpha-1 go out very, very soon so that folks
can really start using it.
--jason
> -----Original Message-----
> From: Jason Dillon [mailto:jason.dillon@gmail.com] On Behalf Of Jason
> Dillon
> Sent: Tuesday, April 03, 2007 3:51 PM
> To: Maven Developers List
> Subject: Re: maven-enforcer-plugin
>
> * * *
>
> Is it close to time for a release of 1.0-alpha-1 of this puppy yet?
>
> --jason
>
>
> On Apr 2, 2007, at 7:31 PM, Brian E. Fox wrote:
>
>> Ok, a little more refactoring. The Custom rules can now get to the
>> ExpressionEvaluator so they can get pretty much anything a plugin
>> could
>> get. The sites are updated to contain info about the standard rules
>> and
>> the custom rule creation:
>> http://maven.apache.org/plugins/maven-enforcer-plugin/
>> http://maven.apache.org/shared/maven-enforcer-rule-api/index.html
>>
>> I'll let this linger for a day or so and then call a vote if nothing
>> turns up.
>>
>> Thanks,
>> Brian
>>
>> -----Original Message-----
>> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
>> Sent: Thursday, March 29, 2007 11:59 PM
>> To: Maven Developers List
>> Subject: RE: maven-enforcer-plugin
>>
>> I reimplemented the enforcer plugin along the lines of Jason D's
>> idea[1]
>> and I think this is a much more extensible solution. The rules now
>> implement a common interface in shared/maven-enforcer-rule-api and
>> users
>> will be able to inject their own custom rules. By defining the
>> interface
>> external to the plugin, the Lint idea that JVZ put out[2] should be
>> able
>> to invoke these rules, as will IDEs.
>>
>> Please take a look at the site to see how the plugin works and
>> provide
>> any suggestions. I still need to document how to create your own
>> rules
>> and inject them, but I believe everything else is covered. A
>> snapshot of
>> 1.0-alpha-1 has also been deployed for testing. (I believe
>> Geronimo is
>> already using it)
>>
>> http://maven.apache.org/plugins/maven-enforcer-plugin (just
>> deployed,
>> may take a while to refresh)
>>
>> [1]
>> http://www.nabble.com/maven-enforcer-plugin-
>> tf3431452s177.html#a9565974
>> [2] http://www.nabble.com/Maven-Lint-tf3462956s177.html#a9661545
>>
>> -----Original Message-----
>> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
>> Sent: Tuesday, March 20, 2007 12:05 AM
>> To: Maven Developers List
>> Subject: maven-enforcer-plugin
>>
>> There is a new plugin that I'd like to get some feedback on,
>> particularly on non-windows os's and the unit tests.
>>
>>
>>
>> The maven-enforcer-plugin picks up where <prerequisites> leaves off
>> and
>> allows control over the maven, jdk and os versions of a build.
>>
>>
>>
>> This plugin was initially conceived here:
>>
>> http://www.nabble.com/Control-of-maven-using-prerequisites-
>> tf3231437s177
>> .html#a8979318
>>
>> And here:
>>
>> http://www.nabble.com/Why-is-prerequisites-not-inherited--
>> tf3236197s177.
>> html#a9016296
>>
>>
>>
>> 1.0-alpha-1-SNAPSHOT is deployed and the site is here:
>> http://maven.apache.org/plugins/maven-enforcer-plugin/ (just
>> deployed so
>> give it a little bit to completely update)
>>
>>
>>
>> If all goes well and no major issues are uncovered, then I think it's
>> ready for staging and a vote.
>>
>>
>>
>> Thanks,
>>
>> Brian
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: maven-enforcer-plugin
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
> The Require OS Version rules docs is using <goal>os</goal> instead of
><goal>require</goal> (or <goal>require-once</goal>).
Good catch. I'll make that change.
> Is it close to time for a release of 1.0-alpha-1 of this puppy yet?
Getting there. I want to explore Jerome's comments about reports and a
vistor pattern. I haven't spent a lot of time thinking about it, but I'm
not sure how a visitor would help here. We really are only interested in
the message coming back. A report mojo could catch all the rule results
and report them. Comments? What am I missing?
I don't want to do a release until we can be relatively sure the
interface for the rules won't change.
-----Original Message-----
From: Jason Dillon [mailto:jason.dillon@gmail.com] On Behalf Of Jason
Dillon
Sent: Tuesday, April 03, 2007 3:51 PM
To: Maven Developers List
Subject: Re: maven-enforcer-plugin
* * *
Is it close to time for a release of 1.0-alpha-1 of this puppy yet?
--jason
On Apr 2, 2007, at 7:31 PM, Brian E. Fox wrote:
> Ok, a little more refactoring. The Custom rules can now get to the
> ExpressionEvaluator so they can get pretty much anything a plugin
> could
> get. The sites are updated to contain info about the standard rules
> and
> the custom rule creation:
> http://maven.apache.org/plugins/maven-enforcer-plugin/
> http://maven.apache.org/shared/maven-enforcer-rule-api/index.html
>
> I'll let this linger for a day or so and then call a vote if nothing
> turns up.
>
> Thanks,
> Brian
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, March 29, 2007 11:59 PM
> To: Maven Developers List
> Subject: RE: maven-enforcer-plugin
>
> I reimplemented the enforcer plugin along the lines of Jason D's
> idea[1]
> and I think this is a much more extensible solution. The rules now
> implement a common interface in shared/maven-enforcer-rule-api and
> users
> will be able to inject their own custom rules. By defining the
> interface
> external to the plugin, the Lint idea that JVZ put out[2] should be
> able
> to invoke these rules, as will IDEs.
>
> Please take a look at the site to see how the plugin works and provide
> any suggestions. I still need to document how to create your own rules
> and inject them, but I believe everything else is covered. A
> snapshot of
> 1.0-alpha-1 has also been deployed for testing. (I believe Geronimo is
> already using it)
>
> http://maven.apache.org/plugins/maven-enforcer-plugin (just deployed,
> may take a while to refresh)
>
> [1]
> http://www.nabble.com/maven-enforcer-plugin-
> tf3431452s177.html#a9565974
> [2] http://www.nabble.com/Maven-Lint-tf3462956s177.html#a9661545
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Tuesday, March 20, 2007 12:05 AM
> To: Maven Developers List
> Subject: maven-enforcer-plugin
>
> There is a new plugin that I'd like to get some feedback on,
> particularly on non-windows os's and the unit tests.
>
>
>
> The maven-enforcer-plugin picks up where <prerequisites> leaves off
> and
> allows control over the maven, jdk and os versions of a build.
>
>
>
> This plugin was initially conceived here:
>
> http://www.nabble.com/Control-of-maven-using-prerequisites-
> tf3231437s177
> .html#a8979318
>
> And here:
>
> http://www.nabble.com/Why-is-prerequisites-not-inherited--
> tf3236197s177.
> html#a9016296
>
>
>
> 1.0-alpha-1-SNAPSHOT is deployed and the site is here:
> http://maven.apache.org/plugins/maven-enforcer-plugin/ (just
> deployed so
> give it a little bit to completely update)
>
>
>
> If all goes well and no major issues are uncovered, then I think it's
> ready for staging and a vote.
>
>
>
> Thanks,
>
> Brian
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-enforcer-plugin
Posted by Jason Dillon <ja...@planet57.com>.
The Require OS Version rules docs is using <goal>os</goal> instead of
<goal>require</goal> (or <goal>require-once</goal>).
* * *
Is it close to time for a release of 1.0-alpha-1 of this puppy yet?
--jason
On Apr 2, 2007, at 7:31 PM, Brian E. Fox wrote:
> Ok, a little more refactoring. The Custom rules can now get to the
> ExpressionEvaluator so they can get pretty much anything a plugin
> could
> get. The sites are updated to contain info about the standard rules
> and
> the custom rule creation:
> http://maven.apache.org/plugins/maven-enforcer-plugin/
> http://maven.apache.org/shared/maven-enforcer-rule-api/index.html
>
> I'll let this linger for a day or so and then call a vote if nothing
> turns up.
>
> Thanks,
> Brian
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, March 29, 2007 11:59 PM
> To: Maven Developers List
> Subject: RE: maven-enforcer-plugin
>
> I reimplemented the enforcer plugin along the lines of Jason D's
> idea[1]
> and I think this is a much more extensible solution. The rules now
> implement a common interface in shared/maven-enforcer-rule-api and
> users
> will be able to inject their own custom rules. By defining the
> interface
> external to the plugin, the Lint idea that JVZ put out[2] should be
> able
> to invoke these rules, as will IDEs.
>
> Please take a look at the site to see how the plugin works and provide
> any suggestions. I still need to document how to create your own rules
> and inject them, but I believe everything else is covered. A
> snapshot of
> 1.0-alpha-1 has also been deployed for testing. (I believe Geronimo is
> already using it)
>
> http://maven.apache.org/plugins/maven-enforcer-plugin (just deployed,
> may take a while to refresh)
>
> [1]
> http://www.nabble.com/maven-enforcer-plugin-
> tf3431452s177.html#a9565974
> [2] http://www.nabble.com/Maven-Lint-tf3462956s177.html#a9661545
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Tuesday, March 20, 2007 12:05 AM
> To: Maven Developers List
> Subject: maven-enforcer-plugin
>
> There is a new plugin that I'd like to get some feedback on,
> particularly on non-windows os's and the unit tests.
>
>
>
> The maven-enforcer-plugin picks up where <prerequisites> leaves off
> and
> allows control over the maven, jdk and os versions of a build.
>
>
>
> This plugin was initially conceived here:
>
> http://www.nabble.com/Control-of-maven-using-prerequisites-
> tf3231437s177
> .html#a8979318
>
> And here:
>
> http://www.nabble.com/Why-is-prerequisites-not-inherited--
> tf3236197s177.
> html#a9016296
>
>
>
> 1.0-alpha-1-SNAPSHOT is deployed and the site is here:
> http://maven.apache.org/plugins/maven-enforcer-plugin/ (just
> deployed so
> give it a little bit to completely update)
>
>
>
> If all goes well and no major issues are uncovered, then I think it's
> ready for staging and a vote.
>
>
>
> Thanks,
>
> Brian
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org