Hi Norbert,
I have updaated PR #82 with comment on GitHub.
The Ubuntu builds fail.
I would prefer keeping the test anyway.
Try to find a solution for Ubuntu as well; otherwise use JUnit assumption
statement
assumeThat( os, anyOf( is( "Windows" ), is( "Ubuntu1" ) ) )
in the particular IT method, p
+1
On Jan 24, 2015, at 5:25 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 34 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19420
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MENFORCER%20AND
Hi,
We solved 34 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19420
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MENFORCER%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Stag
Hi,
The vote has passed with the following result:
+1 (binding): Jason van Zyl, Hervé Boutemy, Karl Heinz Marbaise
+1 (non binding): none
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
-
To
Hi,
yeah i think the idea of it was to move to 2.0...was originally thought
of giving up Maven 2 support...which looks currently not very wise...I
would say next step version 3.0 should remove the Maven 2 support...
Unfortunately i can't take a look into Olivier's thoughts ;-)...
Kind regard
I see the responsible commit, but no reason why.
Revision: 1506898
Author: olamy
Date: donderdag 25 juli 2013 13:19:57
Message:
bump to 2.0-SNAPSHOT version
Modified : /maven/enforcer/trunk/enforcer-api/pom.xml
Modified : /maven/enforcer/trunk/enforcer-rules/pom.xml
Modified : /maven/enforce
Hi Mirko,
I have moved the issue to 2.0 and started the release, cause your mail
remembered me for it...
Cause i wanted to go for a release anyway...
The trunk has 2.0 cause there had been a bump but the version is
1.4...so i will start the release process for 1.4 cause we don't stop
suppor
Hello everybody,
right now 34 of 35 issues for enforcer-1.4 are resolved. The open
issue[1] is a feature
request for a new rule concerning distributionManagement in non-parent poms.
As there seems no real consensus how to deal with this one, I would
set the fixed version for MENFORCER-174 to vers
+1
Regards,
Hervé
Le mercredi 21 janvier 2015 22:17:25 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11990&version=198
> 65
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNav
+1
On Jan 21, 2015, at 4:17 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11990&version=19865
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=XX
+1
On Jan 24, 2015, at 10:22 AM, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 9 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&version=20646
>
> There are still a couple of issues left in JIRA:
> https://jira.codehaus.org/issues/?jql=project%20%3D%20MDEP%20AND%20
Hi,
here my +1
Kind regards
Karl Heinz Marbaise
On 1/24/15 4:22 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 9 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&version=20646
There are still a couple of issues left in JIRA:
https://jira.codehaus.org/issues/?jql=projec
Hi,
We solved 9 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&version=20646
There are still a couple of issues left in JIRA:
https://jira.codehaus.org/issues/?jql=project%20%3D%20MDEP%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging
Hi
here is my +1...
two other binding VOTE's needed...
Kind regards
Karl Heinz Marbaise
On 1/21/15 10:17 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11990&version=19865
There are still a couple of issues left in JIRA:
htt
14 matches
Mail list logo