Hi,
I think it's too early to drop M2 support for plugins.
One of the reasons for giving M2 the EOL status is because there was no
development on this branch anymore, the focus was on M3.
In most cases plugins don't need M3 specific features, M2 is sufficient,
in which case there's no need to force M3.
We could however improve some documentation like:
- refer to the archives
- refer to a continuous integration server
- refer to maven-invoker-plugin#mavenHome in order to *run*/test with an
older version of Maven even though *building* the plugin requires a more
recent version.
thanks,
Robert
Op Sat, 26 Apr 2014 18:53:44 +0200 schreef Rickard von Essen
<rickard.von.es...@gmail.com>:
Hi all,
I was just about to do some testing to prepare for a new release for
rpm-maven-plugin and couldn't get hold of maven 2.2.1 and realized that
it
is EOL since 2014-02-18. (http://maven.apache.org/maven-2.x-eol.html)
This makes it hard to get a hold of Maven 2 for dev and test. Is this
time
for us to drop (official) support for Maven 2 ?
If so, I guess 3.0.5 should be the recommended lowest Maven version?
If we want to keep Maven 2 support maybe we should clearly link to:
http://archive.apache.org/dist/maven/binaries/
to help contributors to find it.
Regards
Rickard von Essen
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
