Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-25 Thread Mirko Friedenhagen
Hello Karl-Heinz,

I added a patch at the MENFORCER-182.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Sat, Jan 25, 2014 at 1:39 PM, Karl Heinz Marbaise  wrote:
> Hello Mirko,
>
>> Hello,
>>
>>
>> I am afraid the only documentation is in the ticket, right now. I could
>> try
>> to find a place this evening and submit a patch.
>
>
> It would be great if you find the time, but take your time, cause there are
> other issues which have to be fixed first
>
> I have created an issue for the documentation
> http://jira.codehaus.org/browse/MENFORCER-182
>
> Kind regards
> Karl Heinz
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-25 Thread Karl Heinz Marbaise

Hi Hervé,

> I just fixed it

Thanks.



while testing, I found that there is an IT failure with Maven 3.1.1: I added a
Jenkins job to reproduce, and it failed as expected


Seen it...I have created a separate issue for it

http://jira.codehaus.org/browse/MENFORCER-181

But unfortunately i can't take a look into the workspace of the Jenkins


I saw too that actual trunk is numbered 2.0-SNAPSHOT: I don't know if some
substantial changes have been done or not


There some changes which are related to WARN/ERROR behaviour ...i don't 
know if it's worth to make a jump from 1.3 to 2.0 currently we go 
from 1.3.1 to 1.4 ...but it's no problem to change that into 2.0...


I just want to summarize some changes for the next release what ever how 
we name it ;-)



Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-25 Thread Karl Heinz Marbaise

Hello Mirko,
> Hello,


I am afraid the only documentation is in the ticket, right now. I could try
to find a place this evening and submit a patch.


It would be great if you find the time, but take your time, cause there 
are other issues which have to be fixed first


I have created an issue for the documentation
http://jira.codehaus.org/browse/MENFORCER-182

Kind regards
Karl Heinz


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-25 Thread Hervé BOUTEMY
I just fixed it

while testing, I found that there is an IT failure with Maven 3.1.1: I added a 
Jenkins job to reproduce, and it failed as expected

I saw too that actual trunk is numbered 2.0-SNAPSHOT: I don't know if some 
substantial changes have been done or not

Regards,

Hervé

Le vendredi 24 janvier 2014 15:53:01 Robert Scholte a écrit :
> Karl Heinz,
> 
> you might hit MENFORCER-161[1], unless Hervé did a fix regarding the
> scm-publish on this project.
> 
> Robert
> 
> [1] https://jira.codehaus.org/browse/MENFORCER-161
> 
> Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise
> 
> :
> > Hi,
> > 
> > i just want to know on what basis releases will be created...
> > 
> > Currently i would suggest to create a Release 1.3.2 of the
> > maven-enforcer-plugin...
> > 
> > In Jira the list
> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=1
> > 9935
> > 
> > for 1.3.2 contains a number of bug fixes...
> > 
> > Are there any objections to get a release 1.3.2 out of the door...
> > 
> > I would like to fix one or two more issues...but i want to know how the
> > mood is about creating a new release of Maven-Enforcer-Plugin
> > 
> > Kind Regards
> > Karl Heinz Marbaise
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Mirko Friedenhagen
Hello,

I am afraid the only documentation is in the ticket, right now. I could try
to find a place this evening and submit a patch.

Regards
Mirko
-- 
Sent from my mobile
On Jan 24, 2014 11:31 PM, "Karl Heinz Marbaise"  wrote:

> Hi Robert,
> Hi Mirko,
>
>
> > Indeed, I couldn't remember the reason for 1.4 (nor with a quick scan
>
>> through Jira), but this was it.
>>
>
> Thanks for the hint...
>
> Ok. i will move the issues to 1.4 ...so new functionality isdefinitely
> a good reason for 1.4 instead of 1.3.2 ...
>
> So MENFORCER-160 is implemented based on a quick dive into the code (and
> based on your hints) and MENFORCER-159 not...so i remove MENFORCER-159 from
> the view for 1.4 release...
>
>
> Thanks for clearing up things...
>
> BTW: Do you know if the new behaviour is documented for the user somewhere
> ? I couldn't find something...may be lose sight of it.
>
>
> Kind regards
> Karl Heinz
>
>
>
>> Robert
>>
>> Op Fri, 24 Jan 2014 22:30:38 +0100 schreef Mirko Friedenhagen
>> :
>>
>>  Karl Heinz,
>>>
>>> another thing: because MENFORCER-160 introduces a new interface which
>>> is implemented by AbstractStandardEnforcerRule maybe version 1.4 would
>>> be a better version number than 1.3.2, as it introduces a new
>>> functionality.
>>> Regards Mirko
>>> --
>>> http://illegalstateexception.blogspot.com/
>>> https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
>>> https://bitbucket.org/mfriedenhagen/
>>>
>>>
>>> On Fri, Jan 24, 2014 at 10:18 PM, Mirko Friedenhagen
>>>  wrote:
>>>
 Karl Heinz,

 one thing: MENFORCER-159 is a duplicate of MENFORCER-160 (or better it
 is an alternative approach), so probably should not be mentioned.

 Regards
 Mirko
 Regards Mirko
 --
 http://illegalstateexception.blogspot.com/
 https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
 https://bitbucket.org/mfriedenhagen/


 On Fri, Jan 24, 2014 at 3:53 PM, Robert Scholte
  wrote:

> Karl Heinz,
>
> you might hit MENFORCER-161[1], unless Hervé did a fix regarding the
> scm-publish on this project.
>
> Robert
>
> [1] https://jira.codehaus.org/browse/MENFORCER-161
>
> Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise
> :
>
>
>  Hi,
>>
>> i just want to know on what basis releases will be created...
>>
>> Currently i would suggest to create a Release 1.3.2 of the
>> maven-enforcer-plugin...
>>
>> In Jira the list
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?
>> projectId=11530&version=19935
>>
>>
>> for 1.3.2 contains a number of bug fixes...
>>
>> Are there any objections to get a release 1.3.2 out of the door...
>>
>> I would like to fix one or two more issues...but i want to know how
>> the
>> mood is about creating a new release of Maven-Enforcer-Plugin
>>
>> Kind Regards
>> Karl Heinz Marbaise
>>
>
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Karl Heinz Marbaise

Hi Robert,
Hi Mirko,


> Indeed, I couldn't remember the reason for 1.4 (nor with a quick scan

through Jira), but this was it.


Thanks for the hint...

Ok. i will move the issues to 1.4 ...so new functionality is 	definitely 
a good reason for 1.4 instead of 1.3.2 ...


So MENFORCER-160 is implemented based on a quick dive into the code (and 
based on your hints) and MENFORCER-159 not...so i remove MENFORCER-159 
from the view for 1.4 release...



Thanks for clearing up things...

BTW: Do you know if the new behaviour is documented for the user 
somewhere ? I couldn't find something...may be lose sight of it.



Kind regards
Karl Heinz




Robert

Op Fri, 24 Jan 2014 22:30:38 +0100 schreef Mirko Friedenhagen
:


Karl Heinz,

another thing: because MENFORCER-160 introduces a new interface which
is implemented by AbstractStandardEnforcerRule maybe version 1.4 would
be a better version number than 1.3.2, as it introduces a new
functionality.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Jan 24, 2014 at 10:18 PM, Mirko Friedenhagen
 wrote:

Karl Heinz,

one thing: MENFORCER-159 is a duplicate of MENFORCER-160 (or better it
is an alternative approach), so probably should not be mentioned.

Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Jan 24, 2014 at 3:53 PM, Robert Scholte
 wrote:

Karl Heinz,

you might hit MENFORCER-161[1], unless Hervé did a fix regarding the
scm-publish on this project.

Robert

[1] https://jira.codehaus.org/browse/MENFORCER-161

Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise
:



Hi,

i just want to know on what basis releases will be created...

Currently i would suggest to create a Release 1.3.2 of the
maven-enforcer-plugin...

In Jira the list

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19935


for 1.3.2 contains a number of bug fixes...

Are there any objections to get a release 1.3.2 out of the door...

I would like to fix one or two more issues...but i want to know how
the
mood is about creating a new release of Maven-Enforcer-Plugin

Kind Regards
Karl Heinz Marbaise



Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Robert Scholte
Indeed, I couldn't remember the reason for 1.4 (nor with a quick scan  
through Jira), but this was it.


Robert

Op Fri, 24 Jan 2014 22:30:38 +0100 schreef Mirko Friedenhagen  
:



Karl Heinz,

another thing: because MENFORCER-160 introduces a new interface which
is implemented by AbstractStandardEnforcerRule maybe version 1.4 would
be a better version number than 1.3.2, as it introduces a new
functionality.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Jan 24, 2014 at 10:18 PM, Mirko Friedenhagen
 wrote:

Karl Heinz,

one thing: MENFORCER-159 is a duplicate of MENFORCER-160 (or better it
is an alternative approach), so probably should not be mentioned.

Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Jan 24, 2014 at 3:53 PM, Robert Scholte   
wrote:

Karl Heinz,

you might hit MENFORCER-161[1], unless Hervé did a fix regarding the
scm-publish on this project.

Robert

[1] https://jira.codehaus.org/browse/MENFORCER-161

Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise
:



Hi,

i just want to know on what basis releases will be created...

Currently i would suggest to create a Release 1.3.2 of the
maven-enforcer-plugin...

In Jira the list

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19935

for 1.3.2 contains a number of bug fixes...

Are there any objections to get a release 1.3.2 out of the door...

I would like to fix one or two more issues...but i want to know how  
the

mood is about creating a new release of Maven-Enforcer-Plugin

Kind Regards
Karl Heinz Marbaise


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Mirko Friedenhagen
Karl Heinz,

another thing: because MENFORCER-160 introduces a new interface which
is implemented by AbstractStandardEnforcerRule maybe version 1.4 would
be a better version number than 1.3.2, as it introduces a new
functionality.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Jan 24, 2014 at 10:18 PM, Mirko Friedenhagen
 wrote:
> Karl Heinz,
>
> one thing: MENFORCER-159 is a duplicate of MENFORCER-160 (or better it
> is an alternative approach), so probably should not be mentioned.
>
> Regards
> Mirko
> Regards Mirko
> --
> http://illegalstateexception.blogspot.com/
> https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
> https://bitbucket.org/mfriedenhagen/
>
>
> On Fri, Jan 24, 2014 at 3:53 PM, Robert Scholte  wrote:
>> Karl Heinz,
>>
>> you might hit MENFORCER-161[1], unless Hervé did a fix regarding the
>> scm-publish on this project.
>>
>> Robert
>>
>> [1] https://jira.codehaus.org/browse/MENFORCER-161
>>
>> Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise
>> :
>>
>>
>>> Hi,
>>>
>>> i just want to know on what basis releases will be created...
>>>
>>> Currently i would suggest to create a Release 1.3.2 of the
>>> maven-enforcer-plugin...
>>>
>>> In Jira the list
>>>
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19935
>>>
>>> for 1.3.2 contains a number of bug fixes...
>>>
>>> Are there any objections to get a release 1.3.2 out of the door...
>>>
>>> I would like to fix one or two more issues...but i want to know how the
>>> mood is about creating a new release of Maven-Enforcer-Plugin
>>>
>>> Kind Regards
>>> Karl Heinz Marbaise
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Mirko Friedenhagen
Karl Heinz,

one thing: MENFORCER-159 is a duplicate of MENFORCER-160 (or better it
is an alternative approach), so probably should not be mentioned.

Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Jan 24, 2014 at 3:53 PM, Robert Scholte  wrote:
> Karl Heinz,
>
> you might hit MENFORCER-161[1], unless Hervé did a fix regarding the
> scm-publish on this project.
>
> Robert
>
> [1] https://jira.codehaus.org/browse/MENFORCER-161
>
> Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise
> :
>
>
>> Hi,
>>
>> i just want to know on what basis releases will be created...
>>
>> Currently i would suggest to create a Release 1.3.2 of the
>> maven-enforcer-plugin...
>>
>> In Jira the list
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19935
>>
>> for 1.3.2 contains a number of bug fixes...
>>
>> Are there any objections to get a release 1.3.2 out of the door...
>>
>> I would like to fix one or two more issues...but i want to know how the
>> mood is about creating a new release of Maven-Enforcer-Plugin
>>
>> Kind Regards
>> Karl Heinz Marbaise
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Robert Scholte

Karl Heinz,

you might hit MENFORCER-161[1], unless Hervé did a fix regarding the  
scm-publish on this project.


Robert

[1] https://jira.codehaus.org/browse/MENFORCER-161

Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise  
:



Hi,

i just want to know on what basis releases will be created...

Currently i would suggest to create a Release 1.3.2 of the  
maven-enforcer-plugin...


In Jira the list
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19935

for 1.3.2 contains a number of bug fixes...

Are there any objections to get a release 1.3.2 out of the door...

I would like to fix one or two more issues...but i want to know how the  
mood is about creating a new release of Maven-Enforcer-Plugin


Kind Regards
Karl Heinz Marbaise


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Stephen Connolly
Well the biggest blocker for cutting releases is getting your binding
votes...

My policy is cut releases until the PMC starts complaining that you are
cutting too many releases... ;-)

I haven't seen any of us complain about releases being too frequent
*ever*...

If you think it is ready for a release now, then as a committer you only
have to stand up and say I am cutting a release...

Good manners is to give 24-72hr notice that you will be cutting a
release... but for a single plugin with nobody else having committed
anything in the past 72hr and no sign of activity other than your own in
JIRA, a quick ping on IRC and the mailing list with a 1-4h wait is probably
fine... after all it's only a plugin and the release builds of those are
fast...

If you were cutting a release of core or a shared component, then I would
think a 72h heads up to ensure that nobody else is working on patching
something would be strongly encouraged... OTOH if you have an issue you see
as critical...

This should be self governing... if you cut too often or with too little
improvement... attracting PMC binding votes will become harder over time...

But as I already said... we are not at the stage of even 1 release vote per
week... so you shouldn't have issues getting 3 PMC members to at least take
a look at a plugin release candidate for a vote

-Stephen


On 24 January 2014 09:22, Karl Heinz Marbaise  wrote:

> Hi,
>
> i just want to know on what basis releases will be created...
>
> Currently i would suggest to create a Release 1.3.2 of the
> maven-enforcer-plugin...
>
> In Jira the list
> http://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=11530&version=19935
>
> for 1.3.2 contains a number of bug fixes...
>
> Are there any objections to get a release 1.3.2 out of the door...
>
> I would like to fix one or two more issues...but i want to know how the
> mood is about creating a new release of Maven-Enforcer-Plugin
>
> Kind Regards
> Karl Heinz Marbaise
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Q: Maven-Enforcer-Plugin - Release 1.3.2 ?

2014-01-24 Thread Karl Heinz Marbaise

Hi,

i just want to know on what basis releases will be created...

Currently i would suggest to create a Release 1.3.2 of the 
maven-enforcer-plugin...


In Jira the list
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19935

for 1.3.2 contains a number of bug fixes...

Are there any objections to get a release 1.3.2 out of the door...

I would like to fix one or two more issues...but i want to know how the 
mood is about creating a new release of Maven-Enforcer-Plugin


Kind Regards
Karl Heinz Marbaise


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Maven Enforcer Plugin Release Request

2012-11-20 Thread Jason van Zyl
While that sounds enticing... I'll stick with the enforcer release :-)

Happy to take a look later in the week once all the Maven 3.1.0 dependencies 
are dealt with.

On Nov 20, 2012, at 1:28 PM, Benson Margulies  wrote:

> Hey Jason,
> 
> I can knock off an enforcer release even intoxicated by acute turkey
> poisoning. On the other hand, I don't know enough to look for a better
> solution to the forked execution issue that we've been discussing with
> respect to the site plugin. Can I interest you in swapping?
> 
> --benson
> 
> 
> On Tue, Nov 20, 2012 at 12:02 PM, Jason van Zyl  wrote:
>> Sure, I can take a look as I'm doing releases this week.
>> 
>> Hervé, you mind if I push out MENFORCER-144 to the next version so I can 
>> stage a release?
>> 
>> https://jira.codehaus.org/secure/IssueNavigator.jspa?fixfor=18491&pid=11530&reset=true&show=View+%26gt%3B%26gt%3B
>> 
>> On Nov 20, 2012, at 11:54 AM, Josh Beitelspacher  wrote:
>> 
>>> Would it be possible to get a new release of the maven enforcer plugin
>>> sometime soon? I've been eagerly awaiting a release with the fix for
>>> http://jira.codehaus.org/browse/MENFORCER-135.
>>> 
>>> Currently my build output is 2139 lines, of which 1701 lines (~80%) is INFO
>>> messages from the enforcer plugin. A brief sample is included below:
>>> 
>>> [INFO] org.apache.cxf:cxf-rt-transports-local 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-ws-security 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> 
>>> The bug that caused this has been fixed since July, but has yet to be
>>> included in a new release.
>>> 
>>> Thanks,
>>> Josh
>> 
>> Thanks,
>> 
>> Jason
>> 
>> --
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> -
>> 
>> The modern conservative is engaged in one of man's oldest exercises in moral 
>> philosophy; that is,
>> the search for a superior moral justification for selfishness.
>> 
>> -- John Kenneth Galbraith
>> 
>> 
>> 
>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-








Re: Maven Enforcer Plugin Release Request

2012-11-20 Thread Jason van Zyl
No rush. Just figured while I'm in the release monkey seat I would try to push 
it out.

On Nov 20, 2012, at 2:53 PM, Hervé BOUTEMY  wrote:

> MENFORCER-144 fixed
> 
> I'd like to MENFORCER-145 before the release, please wait a few more hours
> 
> Regards,
> 
> Hervé
> 
> Le mardi 20 novembre 2012 12:02:40 Jason van Zyl a écrit :
>> Sure, I can take a look as I'm doing releases this week.
>> 
>> Hervé, you mind if I push out MENFORCER-144 to the next version so I can
>> stage a release?
>> 
>> https://jira.codehaus.org/secure/IssueNavigator.jspa?fixfor=18491&pid=11530&;
>> reset=true&show=View+%26gt%3B%26gt%3B
>> On Nov 20, 2012, at 11:54 AM, Josh Beitelspacher  wrote:
>>> Would it be possible to get a new release of the maven enforcer plugin
>>> sometime soon? I've been eagerly awaiting a release with the fix for
>>> http://jira.codehaus.org/browse/MENFORCER-135.
>>> 
>>> Currently my build output is 2139 lines, of which 1701 lines (~80%) is
>>> INFO
>>> messages from the enforcer plugin. A brief sample is included below:
>>> 
>>> [INFO] org.apache.cxf:cxf-rt-transports-local 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-ws-security 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>> 
>>> The bug that caused this has been fixed since July, but has yet to be
>>> included in a new release.
>>> 
>>> Thanks,
>>> Josh
>> 
>> Thanks,
>> 
>> Jason
>> 
>> --
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> -
>> 
>> The modern conservative is engaged in one of man's oldest exercises in moral
>> philosophy; that is, the search for a superior moral justification for
>> selfishness.
>> 
>> -- John Kenneth Galbraith
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

Selfish deeds are the shortest path to self destruction.

 -- The Seven Samuari, Akira Kurosawa







Re: Maven Enforcer Plugin Release Request

2012-11-20 Thread Hervé BOUTEMY
MENFORCER-144 fixed

I'd like to MENFORCER-145 before the release, please wait a few more hours

Regards,

Hervé

Le mardi 20 novembre 2012 12:02:40 Jason van Zyl a écrit :
> Sure, I can take a look as I'm doing releases this week.
> 
> Hervé, you mind if I push out MENFORCER-144 to the next version so I can
> stage a release?
> 
> https://jira.codehaus.org/secure/IssueNavigator.jspa?fixfor=18491&pid=11530&;
> reset=true&show=View+%26gt%3B%26gt%3B
> On Nov 20, 2012, at 11:54 AM, Josh Beitelspacher  wrote:
> > Would it be possible to get a new release of the maven enforcer plugin
> > sometime soon? I've been eagerly awaiting a release with the fix for
> > http://jira.codehaus.org/browse/MENFORCER-135.
> > 
> > Currently my build output is 2139 lines, of which 1701 lines (~80%) is
> > INFO
> > messages from the enforcer plugin. A brief sample is included below:
> > 
> > [INFO] org.apache.cxf:cxf-rt-transports-local 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-ws-security 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> > 
> > The bug that caused this has been fixed since July, but has yet to be
> > included in a new release.
> > 
> > Thanks,
> > Josh
> 
> Thanks,
> 
> Jason
> 
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
> 
> The modern conservative is engaged in one of man's oldest exercises in moral
> philosophy; that is, the search for a superior moral justification for
> selfishness.
> 
>  -- John Kenneth Galbraith

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Maven Enforcer Plugin Release Request

2012-11-20 Thread Benson Margulies
Hey Jason,

I can knock off an enforcer release even intoxicated by acute turkey
poisoning. On the other hand, I don't know enough to look for a better
solution to the forked execution issue that we've been discussing with
respect to the site plugin. Can I interest you in swapping?

--benson


On Tue, Nov 20, 2012 at 12:02 PM, Jason van Zyl  wrote:
> Sure, I can take a look as I'm doing releases this week.
>
> Hervé, you mind if I push out MENFORCER-144 to the next version so I can 
> stage a release?
>
> https://jira.codehaus.org/secure/IssueNavigator.jspa?fixfor=18491&pid=11530&reset=true&show=View+%26gt%3B%26gt%3B
>
> On Nov 20, 2012, at 11:54 AM, Josh Beitelspacher  wrote:
>
>> Would it be possible to get a new release of the maven enforcer plugin
>> sometime soon? I've been eagerly awaiting a release with the fix for
>> http://jira.codehaus.org/browse/MENFORCER-135.
>>
>> Currently my build output is 2139 lines, of which 1701 lines (~80%) is INFO
>> messages from the enforcer plugin. A brief sample is included below:
>>
>> [INFO] org.apache.cxf:cxf-rt-transports-local 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-ws-security 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
>>
>> The bug that caused this has been fixed since July, but has yet to be
>> included in a new release.
>>
>> Thanks,
>> Josh
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> The modern conservative is engaged in one of man's oldest exercises in moral 
> philosophy; that is,
> the search for a superior moral justification for selfishness.
>
>  -- John Kenneth Galbraith
>
>
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Maven Enforcer Plugin Release Request

2012-11-20 Thread Jason van Zyl
Sure, I can take a look as I'm doing releases this week.

Hervé, you mind if I push out MENFORCER-144 to the next version so I can stage 
a release?

https://jira.codehaus.org/secure/IssueNavigator.jspa?fixfor=18491&pid=11530&reset=true&show=View+%26gt%3B%26gt%3B

On Nov 20, 2012, at 11:54 AM, Josh Beitelspacher  wrote:

> Would it be possible to get a new release of the maven enforcer plugin
> sometime soon? I've been eagerly awaiting a release with the fix for
> http://jira.codehaus.org/browse/MENFORCER-135.
> 
> Currently my build output is 2139 lines, of which 1701 lines (~80%) is INFO
> messages from the enforcer plugin. A brief sample is included below:
> 
> [INFO] org.apache.cxf:cxf-rt-transports-local 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-ws-security 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> [INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
> 
> The bug that caused this has been fixed since July, but has yet to be
> included in a new release.
> 
> Thanks,
> Josh

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

The modern conservative is engaged in one of man's oldest exercises in moral 
philosophy; that is, 
the search for a superior moral justification for selfishness.

 -- John Kenneth Galbraith







Maven Enforcer Plugin Release Request

2012-11-20 Thread Josh Beitelspacher
Would it be possible to get a new release of the maven enforcer plugin
sometime soon? I've been eagerly awaiting a release with the fix for
http://jira.codehaus.org/browse/MENFORCER-135.

Currently my build output is 2139 lines, of which 1701 lines (~80%) is INFO
messages from the enforcer plugin. A brief sample is included below:

[INFO] org.apache.cxf:cxf-rt-transports-local 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-ws-security 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-api 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0
[INFO] org.apache.cxf:cxf-rt-core 2.7.0 2.7.0

The bug that caused this has been fixed since July, but has yet to be
included in a new release.

Thanks,
Josh


Enforcer plugin release

2008-09-04 Thread Jan Fredrik Wedén
Hi,

What's the status on the Enforcer plugin release these days?

Is it possible to get another alpha out if the pending JIRAs have to
be fixed for 1.0.0? Seems to me that none of the outstanding issues
are bugs which prevents releasing the current work. WDYT?

-- 
- Jan Fredrik Wedén

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