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
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 t
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 issu
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 2
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 reaso
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 imple
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 AbstractStandar
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://
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
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
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 rel
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...
A
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 acu
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
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 versio
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 T
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
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.
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
19 matches
Mail list logo
