2009/6/6 Dennis Lundberg <[email protected]>

> 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: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to