You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dennis Lundberg <de...@apache.org> on 2009/05/15 16:58:28 UTC
[VOTE] Java 5 and Maven Plugins
Hi
Recent discussions about the Checkstyle Plugin has raised the question
of requiring Java 5 in Maven Plugins.
We will IIUC require Java 5 for Maven 2.2. So when do we start using it
in our plugins?
[A] We start using it across the board for the next release of every
plugin that wants to use Java 5 features or needs a dependency that
requires Java 5.
[B] The plugins can start using Java 5 features and/or dependencies. It
is required that the current trunk of the plugin is released first,
targeting Java 1.4. In the announcement for that last Java 1.4 version
of the plugin, we inform the users that this is the last version that
will be able to run on Java 1.4.
[C] The plugins should not use Java 5 features. We can use
retrotranslator, or something similar, to handle dependencies that
require Java 5.
[D] The plugins should not use Java 5 features. We will not update
dependencies unless a "-java14" classified artifact is readily available
from the developers of any dependencies.
If you feel that there are other options we can take, please feel free
to put them into the mix.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE][RESULT] Java 5 and Maven Plugins
Posted by nicolas de loof <ni...@gmail.com>.
2009/6/6 Dennis Lundberg <de...@apache.org>
> Here are the results of this vote. It was somewhat difficult to
> summarize as some of the voters replied +1 to someone else's vote and
> others voted on more than one option.
Maybe you can count my vote a 0.5 for [A] and 0.5 for [B] ;)
> Feel free to correct my
> interpretations below.
>
>
> [A] Nicolas
>
> [B] Nicolas, Brian (my interpretation of what he wrote), Brett, Mark
> (agreeing with Brett), Garvin, Dennis
>
>
> I'll let this mail sit for a couple of days. Then I'll find a suitable
> place in our development guidelines and insert [B] as our preferred way.
>
> Thanks for your votes and input.
>
>
> Dennis Lundberg wrote:
> > Hi
> >
> > Recent discussions about the Checkstyle Plugin has raised the question
> > of requiring Java 5 in Maven Plugins.
> >
> > We will IIUC require Java 5 for Maven 2.2. So when do we start using it
> > in our plugins?
> >
> > [A] We start using it across the board for the next release of every
> > plugin that wants to use Java 5 features or needs a dependency that
> > requires Java 5.
> >
> > [B] The plugins can start using Java 5 features and/or dependencies. It
> > is required that the current trunk of the plugin is released first,
> > targeting Java 1.4. In the announcement for that last Java 1.4 version
> > of the plugin, we inform the users that this is the last version that
> > will be able to run on Java 1.4.
> >
> > [C] The plugins should not use Java 5 features. We can use
> > retrotranslator, or something similar, to handle dependencies that
> > require Java 5.
> >
> > [D] The plugins should not use Java 5 features. We will not update
> > dependencies unless a "-java14" classified artifact is readily available
> > from the developers of any dependencies.
> >
> >
> > If you feel that there are other options we can take, please feel free
> > to put them into the mix.
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
[VOTE][RESULT] Java 5 and Maven Plugins
Posted by Dennis Lundberg <de...@apache.org>.
Here are the results of this vote. It was somewhat difficult to
summarize as some of the voters replied +1 to someone else's vote and
others voted on more than one option. Feel free to correct my
interpretations below.
[A] Nicolas
[B] Nicolas, Brian (my interpretation of what he wrote), Brett, Mark
(agreeing with Brett), Garvin, Dennis
I'll let this mail sit for a couple of days. Then I'll find a suitable
place in our development guidelines and insert [B] as our preferred way.
Thanks for your votes and input.
Dennis Lundberg wrote:
> Hi
>
> Recent discussions about the Checkstyle Plugin has raised the question
> of requiring Java 5 in Maven Plugins.
>
> We will IIUC require Java 5 for Maven 2.2. So when do we start using it
> in our plugins?
>
> [A] We start using it across the board for the next release of every
> plugin that wants to use Java 5 features or needs a dependency that
> requires Java 5.
>
> [B] The plugins can start using Java 5 features and/or dependencies. It
> is required that the current trunk of the plugin is released first,
> targeting Java 1.4. In the announcement for that last Java 1.4 version
> of the plugin, we inform the users that this is the last version that
> will be able to run on Java 1.4.
>
> [C] The plugins should not use Java 5 features. We can use
> retrotranslator, or something similar, to handle dependencies that
> require Java 5.
>
> [D] The plugins should not use Java 5 features. We will not update
> dependencies unless a "-java14" classified artifact is readily available
> from the developers of any dependencies.
>
>
> If you feel that there are other options we can take, please feel free
> to put them into the mix.
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
AW: [VOTE] Java 5 and Maven Plugins
Posted by Mark Struberg <st...@yahoo.de>.
+1
it's a simple trade off. Do we like to punish >=jdk1.5 users or <=jdk1.4 users.
For a production build or in a CI system, plugin versions should be set in the pom anyway. Otherwise a build is not 100% reproduceable.
LieGrue,
strub
----- Ursprüngliche Mail ----
> Von: Brett Porter <br...@apache.org>
> An: Maven Developers List <de...@maven.apache.org>
> Gesendet: Samstag, den 16. Mai 2009, 03:12:56 Uhr
> Betreff: Re: [VOTE] Java 5 and Maven Plugins
>
>
> On 16/05/2009, at 5:06 AM, Stephane Nicoll wrote:
>
> > On Fri, May 15, 2009 at 6:58 PM, Benjamin Bentmann <
> > benjamin.bentmann@udo.edu> wrote:
> >
> >> Daniel Kulp wrote:
> >>
> >> On Fri May 15 2009 12:18:59 pm Brian Fox wrote:
> >>>
> >>>> I don't think we should go out of our way yet to convert everything to
> >>>> java5, preserving 1.4 compatibility (essentially 2.0/2.1 compatibility)
> >>>> should be considered. However if there's a reason, like the checkstyle
> >>>> update requies java 5, then we should do it and set a prerequisite of
> >>>> maven
> >>>> 2.2.0.
> >>>>
> >>>
> >>> I don't think setting a prerequisite of 2.2.0 is a good idea. If the
> >>> plugin will work with 2.0.10 + java 5, then I think we should allow that.
> >>>
> >>
> >> I agree with Dan, the prerequisite on a specific Maven version and a Java
> >> version are two different things. Users can fairly well run plugins
> >> targetting Java 1.5 with a core targetting 1.4.
> >
> >
> > +1
>
> +1, including Brian's original sentiment. Be conservative but not restrictive.
>
> As long as it is clearly documented in the plugin release notes / site (and the
> last version to work with 1.4 should be indicated), I think we can live with the
> occasional auto-upgrade biting people using JDK 1.4 and having to lock down a
> version.
>
> In terms of Dennis' suggestions, I would say my choice is that [B] is best, [A]
> is acceptable.
>
> Cheers,
> Brett
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Java 5 and Maven Plugins
Posted by Brett Porter <br...@apache.org>.
On 16/05/2009, at 5:06 AM, Stephane Nicoll wrote:
> On Fri, May 15, 2009 at 6:58 PM, Benjamin Bentmann <
> benjamin.bentmann@udo.edu> wrote:
>
>> Daniel Kulp wrote:
>>
>> On Fri May 15 2009 12:18:59 pm Brian Fox wrote:
>>>
>>>> I don't think we should go out of our way yet to convert
>>>> everything to
>>>> java5, preserving 1.4 compatibility (essentially 2.0/2.1
>>>> compatibility)
>>>> should be considered. However if there's a reason, like the
>>>> checkstyle
>>>> update requies java 5, then we should do it and set a
>>>> prerequisite of
>>>> maven
>>>> 2.2.0.
>>>>
>>>
>>> I don't think setting a prerequisite of 2.2.0 is a good idea. If
>>> the
>>> plugin will work with 2.0.10 + java 5, then I think we should
>>> allow that.
>>>
>>
>> I agree with Dan, the prerequisite on a specific Maven version and
>> a Java
>> version are two different things. Users can fairly well run plugins
>> targetting Java 1.5 with a core targetting 1.4.
>
>
> +1
+1, including Brian's original sentiment. Be conservative but not
restrictive.
As long as it is clearly documented in the plugin release notes / site
(and the last version to work with 1.4 should be indicated), I think
we can live with the occasional auto-upgrade biting people using JDK
1.4 and having to lock down a version.
In terms of Dennis' suggestions, I would say my choice is that [B] is
best, [A] is acceptable.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Java 5 and Maven Plugins
Posted by Stephane Nicoll <st...@gmail.com>.
On Fri, May 15, 2009 at 6:58 PM, Benjamin Bentmann <
benjamin.bentmann@udo.edu> wrote:
> Daniel Kulp wrote:
>
> On Fri May 15 2009 12:18:59 pm Brian Fox wrote:
>>
>>> I don't think we should go out of our way yet to convert everything to
>>> java5, preserving 1.4 compatibility (essentially 2.0/2.1 compatibility)
>>> should be considered. However if there's a reason, like the checkstyle
>>> update requies java 5, then we should do it and set a prerequisite of
>>> maven
>>> 2.2.0.
>>>
>>
>> I don't think setting a prerequisite of 2.2.0 is a good idea. If the
>> plugin will work with 2.0.10 + java 5, then I think we should allow that.
>>
>
> I agree with Dan, the prerequisite on a specific Maven version and a Java
> version are two different things. Users can fairly well run plugins
> targetting Java 1.5 with a core targetting 1.4.
+1
Stéphane
>
>
>
> Benjamin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Large Systems Suck: This rule is 100% transitive. If you build one, you
suck" -- S.Yegge
Re: [VOTE] Java 5 and Maven Plugins
Posted by Benjamin Bentmann <be...@udo.edu>.
Daniel Kulp wrote:
> On Fri May 15 2009 12:18:59 pm Brian Fox wrote:
>> I don't think we should go out of our way yet to convert everything to
>> java5, preserving 1.4 compatibility (essentially 2.0/2.1 compatibility)
>> should be considered. However if there's a reason, like the checkstyle
>> update requies java 5, then we should do it and set a prerequisite of maven
>> 2.2.0.
>
> I don't think setting a prerequisite of 2.2.0 is a good idea. If the plugin
> will work with 2.0.10 + java 5, then I think we should allow that.
I agree with Dan, the prerequisite on a specific Maven version and a
Java version are two different things. Users can fairly well run plugins
targetting Java 1.5 with a core targetting 1.4.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Java 5 and Maven Plugins
Posted by Daniel Kulp <dk...@apache.org>.
On Fri May 15 2009 12:18:59 pm Brian Fox wrote:
> I don't think we should go out of our way yet to convert everything to
> java5, preserving 1.4 compatibility (essentially 2.0/2.1 compatibility)
> should be considered. However if there's a reason, like the checkstyle
> update requies java 5, then we should do it and set a prerequisite of maven
> 2.2.0.
I don't think setting a prerequisite of 2.2.0 is a good idea. If the plugin
will work with 2.0.10 + java 5, then I think we should allow that. I DON'T
see many people moving to maven 2.2.x for a while.
Dan
> On Fri, May 15, 2009 at 11:05 AM, nicolas de loof
>
> <ni...@gmail.com>wrote:
> > I myself have been very conservative about Java updates because I still
> > have
> > to support Java 1.3 applications. I learned to use Maven with JDK6 and
> > target 1.3 environment.
> > for this reason I'm +1 with [A] or [B] (depending on the status of
> > SNAPSHOT plugins that in some cas include major fix compared to latest
> > release) Nicolas
> >
> > 2009/5/15 Dennis Lundberg <de...@apache.org>
> >
> > > Hi
> > >
> > > Recent discussions about the Checkstyle Plugin has raised the question
> > > of requiring Java 5 in Maven Plugins.
> > >
> > > We will IIUC require Java 5 for Maven 2.2. So when do we start using it
> > > in our plugins?
> > >
> > > [A] We start using it across the board for the next release of every
> > > plugin that wants to use Java 5 features or needs a dependency that
> > > requires Java 5.
> > >
> > > [B] The plugins can start using Java 5 features and/or dependencies. It
> > > is required that the current trunk of the plugin is released first,
> > > targeting Java 1.4. In the announcement for that last Java 1.4 version
> > > of the plugin, we inform the users that this is the last version that
> > > will be able to run on Java 1.4.
> > >
> > > [C] The plugins should not use Java 5 features. We can use
> > > retrotranslator, or something similar, to handle dependencies that
> > > require Java 5.
> > >
> > > [D] The plugins should not use Java 5 features. We will not update
> > > dependencies unless a "-java14" classified artifact is readily
> > > available from the developers of any dependencies.
> > >
> > >
> > > If you feel that there are other options we can take, please feel free
> > > to put them into the mix.
> > >
> > > --
> > > Dennis Lundberg
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Java 5 and Maven Plugins
Posted by Brian Fox <br...@infinity.nu>.
I don't think we should go out of our way yet to convert everything to
java5, preserving 1.4 compatibility (essentially 2.0/2.1 compatibility)
should be considered. However if there's a reason, like the checkstyle
update requies java 5, then we should do it and set a prerequisite of maven
2.2.0.
On Fri, May 15, 2009 at 11:05 AM, nicolas de loof
<ni...@gmail.com>wrote:
> I myself have been very conservative about Java updates because I still
> have
> to support Java 1.3 applications. I learned to use Maven with JDK6 and
> target 1.3 environment.
> for this reason I'm +1 with [A] or [B] (depending on the status of SNAPSHOT
> plugins that in some cas include major fix compared to latest release)
> Nicolas
>
> 2009/5/15 Dennis Lundberg <de...@apache.org>
>
> > Hi
> >
> > Recent discussions about the Checkstyle Plugin has raised the question
> > of requiring Java 5 in Maven Plugins.
> >
> > We will IIUC require Java 5 for Maven 2.2. So when do we start using it
> > in our plugins?
> >
> > [A] We start using it across the board for the next release of every
> > plugin that wants to use Java 5 features or needs a dependency that
> > requires Java 5.
> >
> > [B] The plugins can start using Java 5 features and/or dependencies. It
> > is required that the current trunk of the plugin is released first,
> > targeting Java 1.4. In the announcement for that last Java 1.4 version
> > of the plugin, we inform the users that this is the last version that
> > will be able to run on Java 1.4.
> >
> > [C] The plugins should not use Java 5 features. We can use
> > retrotranslator, or something similar, to handle dependencies that
> > require Java 5.
> >
> > [D] The plugins should not use Java 5 features. We will not update
> > dependencies unless a "-java14" classified artifact is readily available
> > from the developers of any dependencies.
> >
> >
> > If you feel that there are other options we can take, please feel free
> > to put them into the mix.
> >
> > --
> > Dennis Lundberg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: [VOTE] Java 5 and Maven Plugins
Posted by nicolas de loof <ni...@gmail.com>.
I myself have been very conservative about Java updates because I still have
to support Java 1.3 applications. I learned to use Maven with JDK6 and
target 1.3 environment.
for this reason I'm +1 with [A] or [B] (depending on the status of SNAPSHOT
plugins that in some cas include major fix compared to latest release)
Nicolas
2009/5/15 Dennis Lundberg <de...@apache.org>
> Hi
>
> Recent discussions about the Checkstyle Plugin has raised the question
> of requiring Java 5 in Maven Plugins.
>
> We will IIUC require Java 5 for Maven 2.2. So when do we start using it
> in our plugins?
>
> [A] We start using it across the board for the next release of every
> plugin that wants to use Java 5 features or needs a dependency that
> requires Java 5.
>
> [B] The plugins can start using Java 5 features and/or dependencies. It
> is required that the current trunk of the plugin is released first,
> targeting Java 1.4. In the announcement for that last Java 1.4 version
> of the plugin, we inform the users that this is the last version that
> will be able to run on Java 1.4.
>
> [C] The plugins should not use Java 5 features. We can use
> retrotranslator, or something similar, to handle dependencies that
> require Java 5.
>
> [D] The plugins should not use Java 5 features. We will not update
> dependencies unless a "-java14" classified artifact is readily available
> from the developers of any dependencies.
>
>
> If you feel that there are other options we can take, please feel free
> to put them into the mix.
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] Java 5 and Maven Plugins
Posted by Garvin LeClaire <ga...@gmail.com>.
+1 for [B].
This is what I had to do for the Findbugs plugin since Findbugs relies
on Java 5 since . We are still able to use it against Java 1.3 or 1.4
generated code.
Regards,
Garvin LeClaire
garvin.leclaire@gmail.com
Dennis Lundberg wrote:
> Hi
>
> Recent discussions about the Checkstyle Plugin has raised the question
> of requiring Java 5 in Maven Plugins.
>
> We will IIUC require Java 5 for Maven 2.2. So when do we start using it
> in our plugins?
>
> [A] We start using it across the board for the next release of every
> plugin that wants to use Java 5 features or needs a dependency that
> requires Java 5.
>
> [B] The plugins can start using Java 5 features and/or dependencies. It
> is required that the current trunk of the plugin is released first,
> targeting Java 1.4. In the announcement for that last Java 1.4 version
> of the plugin, we inform the users that this is the last version that
> will be able to run on Java 1.4.
>
> [C] The plugins should not use Java 5 features. We can use
> retrotranslator, or something similar, to handle dependencies that
> require Java 5.
>
> [D] The plugins should not use Java 5 features. We will not update
> dependencies unless a "-java14" classified artifact is readily available
> from the developers of any dependencies.
>
>
> If you feel that there are other options we can take, please feel free
> to put them into the mix.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Java 5 and Maven Plugins
Posted by Dennis Lundberg <de...@apache.org>.
I vote for B.
Dennis Lundberg wrote:
> Hi
>
> Recent discussions about the Checkstyle Plugin has raised the question
> of requiring Java 5 in Maven Plugins.
>
> We will IIUC require Java 5 for Maven 2.2. So when do we start using it
> in our plugins?
>
> [A] We start using it across the board for the next release of every
> plugin that wants to use Java 5 features or needs a dependency that
> requires Java 5.
>
> [B] The plugins can start using Java 5 features and/or dependencies. It
> is required that the current trunk of the plugin is released first,
> targeting Java 1.4. In the announcement for that last Java 1.4 version
> of the plugin, we inform the users that this is the last version that
> will be able to run on Java 1.4.
>
> [C] The plugins should not use Java 5 features. We can use
> retrotranslator, or something similar, to handle dependencies that
> require Java 5.
>
> [D] The plugins should not use Java 5 features. We will not update
> dependencies unless a "-java14" classified artifact is readily available
> from the developers of any dependencies.
>
>
> If you feel that there are other options we can take, please feel free
> to put them into the mix.
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org