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