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
