Maven 2.2 and up require Java 5. The only reason to support Java 1.4 is for bug
fixes for 2.0.x. I would suggest that at this point those are only necessary
for really critical errors.
Ralph
On Dec 22, 2010, at 1:30 AM, Stephane Nicoll wrote:
> Shouldn't we switch that in a coherent manner? I
but in my case (invoker plugin) is in jira and already committed :-).
2010/12/22 Stephane Nicoll :
> Shouldn't we switch that in a coherent manner? I am afraid that if
> each plugin changes at their own pace, users will get confused about
> which ones are still compatible with Java 1.4.
>
> How ab
Shouldn't we switch that in a coherent manner? I am afraid that if
each plugin changes at their own pace, users will get confused about
which ones are still compatible with Java 1.4.
How about releasing each plugin with what's in Jira currently and
switch to java 5 for the next major version?
S.
Hi Folks,
Regarding the Dennis vote for changes plugin move to java5.
Do we need such votes for all changes of this type ?
Here I think about invoker plugin, I have moved recently but only with
a jira entry [1]
WDYT ?
Thanks,
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/ol
