If that is the only reason for the release and it can be fixed in an earlier
release, then I see no reason not too.
This is also in line with the general
Maven ethos of not forcing people to upgrade.
-Chris
Sent from my iPhone
On 24/09/2012, at 6:44 AM, Kristian Rosenvold
wrote:
> At the mo
I feel I'm not getting across entriely here; maven3 will be a
requirement to build the plugins on /any/
jdk (not to use them)
The only real problem I see with this is avoiding stuff like
http://jira.codehaus.org/browse/SUREFIRE-896,
which is certainly easier if the full build runs on 2.2.1/jdk1.5
I think both choices are fine. The risk-averse users on Maven 2.2.1 are
probably also not on Java 7 :) Put the other way, requiring a bump to Maven 3
to build plugins on Java 7 sounds reasonable to me.
On 24/09/2012, at 6:56 AM, Dennis Lundberg wrote:
> Hi
>
> We have other developers to thin
Hi
We have other developers to think about as well. Even though might be OK
with requiring Maven 3 to build our plugins, the plugin testing stuff is
used by many other plugins. Since they might not be OK with it, I think
we should do a 1.3 release.
On 2012-09-23 22:44, Kristian Rosenvold wrote:
>
At the moment, most of the plugin it's don't run under java 7 (dont
know about 1.6).
The reasons for this seems to be largely that the version of easymock
that is used in all released versions of plugin-testing
is incompatible with java 7. And since it's easymock classextension,
it looks like upgr
