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 > > <[email protected]>: > > 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: [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: [email protected] For additional commands, e-mail: [email protected]
