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 regards
Karl Heinz Marbaise
On 1/24/15 10:34 PM, Robert Scholte wrote:
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/enforcer/trunk/maven-enforcer-plugin/pom.xml
Modified : /maven/enforcer/trunk/pom.xml
Op Sat, 24 Jan 2015 22:17:47 +0100 schreef Mirko Friedenhagen
<[email protected]>:
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 version 2.0.
One thing I observed: the trunk already has 2.0-SNAPSHOT as version.
Does anyone know why?
Otherwise I would like to cut release 1.4.
Regards
Mirko
[1] https://jira.codehaus.org/browse/MENFORCER-174
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
