You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2015/02/02 12:42:02 UTC
Roadmap Proposal Plugin Releases
Hi,
after some discussions at FOSDEM with Hervé, Kristian and Robert in
Brussels i will summarize some ideas we would like to share here:
Make a final release of all plugins with minium Maven 2.2.1
(prerequisites) and Java 1.5
The current state of this approach can be watched on the dist-tool [2] page.
After that we can start making releases of the plugins which have
minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups in
code etc.)
To make this more clear for the users the plugin versions should be
bumped to 3.0....independant from their current version.
This approach gives us the possibility to make in case of real bugs bug
fix releases of the older plugins for JDK 5 etc. without confusion JDK
5/JDK6 etc.
These are the steps to leave Maven 2 completely behind..Yeah ;-)
Currently we have two (three) exceptions maven-site-plugin (some kind of
special case), maven-scm-publish-plugin and maven-shade-plugin which
already have the Maven 3 requirement.
[1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
[2]
https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Roadmap Proposal Plugin Releases
Posted by Benson Margulies <bi...@gmail.com>.
I'll poke around.
On Wed, Feb 4, 2015 at 4:46 PM, Anders Hammar <an...@hammar.net> wrote:
> ARCHETYPE-431 fixed.
> However, when building I see a bunch of Maven "Build Failure" in the output
> from tests. Don't know if that's expected, but it looks weird. The tests
> pass though, but that could be wrong. Didn't have time to look into that.
> Also, there are some warnings in the build that could be cleaned up.
>
> /Anders
>
> On Wed, Feb 4, 2015 at 3:43 PM, Anders Hammar <an...@hammar.net> wrote:
>
>> I'll have a look.
>>
>> /Anders (mobile)
>> Den 4 feb 2015 14:03 skrev "Benson Margulies" <bi...@gmail.com>:
>>
>> Gents, are you willing to do it and I'll just be RM?
>>>
>>>
>>> On Wed, Feb 4, 2015 at 6:33 AM, Arnaud Héritier <ah...@gmail.com>
>>> wrote:
>>> > +1
>>> >
>>> > On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar <an...@hammar.net>
>>> wrote:
>>> >
>>> >> > Ouch that's an old one :-)
>>> >> >
>>> >> > Yes I was interested to have a 2.3 release but we failed to find the
>>> >> > motivation/time to close 431
>>> >>
>>> >>
>>> >> Yes, I hardly even remember this one. The code seems to be fixed
>>> except the
>>> >> unit test. I'd say we should go for the easiest way so that we could
>>> close
>>> >> this ticket. Then we could create a new one for any remaining work.
>>> >>
>>> >> /Anders
>>> >>
>>> >>
>>> >> >
>>> >> > On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY <herve.boutemy@free.fr
>>> >
>>> >> > wrote:
>>> >> >
>>> >> > > I didn't work on this one for a long time
>>> >> > >
>>> >> > > Anders and Arnaud seem to have problems to decide how to fix and
>>> close
>>> >> > > http://jira.codehaus.org/browse/ARCHETYPE-431
>>> >> > >
>>> >> > > Regards,
>>> >> > >
>>> >> > > Hervé
>>> >> > >
>>> >> > > Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
>>> >> > > > So, I've committed changes to the archetype system that I believe
>>> >> > > > correspond to the 2.2.1 level. What else wants to happen before a
>>> >> > > > release?
>>> >> > > >
>>> >> > > > On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <
>>> herve.boutemy@free.fr
>>> >> >
>>> >> > > wrote:
>>> >> > > > > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
>>> >> > > > >> Hi,
>>> >> > > > >>
>>> >> > > > >> after some discussions at FOSDEM with Hervé, Kristian and
>>> Robert
>>> >> in
>>> >> > > > >> Brussels i will summarize some ideas we would like to share
>>> here:
>>> >> > > > >>
>>> >> > > > >> Make a final release of all plugins with minium Maven 2.2.1
>>> >> > > > >> (prerequisites) and Java 1.5
>>> >> > > > >>
>>> >> > > > >> The current state of this approach can be watched on the
>>> dist-tool
>>> >> > [2]
>>> >> > > > >
>>> >> > > > > page.
>>> >> > > > >
>>> >> > > > >> After that we can start making releases of the plugins which
>>> have
>>> >> > > > >> minimum Maven 3.0 and JDK 6 (I think this will bring many
>>> cleanups
>>> >> > in
>>> >> > > > >> code etc.)
>>> >> > > > >>
>>> >> > > > >> To make this more clear for the users the plugin versions
>>> should
>>> >> be
>>> >> > > > >> bumped to 3.0....independant from their current version.
>>> >> > > > >>
>>> >> > > > >> This approach gives us the possibility to make in case of real
>>> >> bugs
>>> >> > > bug
>>> >> > > > >> fix releases of the older plugins for JDK 5 etc. without
>>> confusion
>>> >> > JDK
>>> >> > > > >> 5/JDK6 etc.
>>> >> > > > >>
>>> >> > > > >> These are the steps to leave Maven 2 completely behind..Yeah
>>> ;-)
>>> >> > > > >>
>>> >> > > > >> Currently we have two (three) exceptions maven-site-plugin
>>> (some
>>> >> > kind
>>> >> > > of
>>> >> > > > >> special case), maven-scm-publish-plugin and maven-shade-plugin
>>> >> which
>>> >> > > > >> already have the Maven 3 requirement.
>>> >> > > > >
>>> >> > > > > more precisely, IMHO, we'll need to document 2 exceptions:
>>> >> > > > > 1. plugins that are already at version 3.x but do not require
>>> Maven
>>> >> > 3:
>>> >> > > > > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
>>> >> > > > > maven-compiler-plugin 2. plugins that require Maven 3 with
>>> version
>>> >> <
>>> >> > > 3.0:
>>> >> > > > > maven-scm-publish-plugin and maven-shade-plugin
>>> >> > > > >
>>> >> > > > > And we'll need to add a documentation in every plugin that
>>> changes
>>> >> > its
>>> >> > > > > requirements to remember to end-users which is the last version
>>> >> that
>>> >> > > > > requires Maven 2
>>> >> > > > > Perhaps something to add to maven-docck-plugin
>>> >> > > > >
>>> >> > > > > Regards,
>>> >> > > > >
>>> >> > > > > Hervé
>>> >> > > > >
>>> >> > > > >> [1]
>>> >> > http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
>>> >> > > > >> [2]
>>> >> > > > >>
>>> >> > >
>>> >> >
>>> >>
>>> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
>>> >> > > > >> es. html
>>> >> > > > >>
>>> >> > > > >>
>>> >> > > > >> Kind regards
>>> >> > > > >> Karl Heinz Marbaise
>>> >> > > > >>
>>> >> > > > >>
>>> >> > ---------------------------------------------------------------------
>>> >> > > > >> 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
>>> >> > > >
>>> >> > > >
>>> ---------------------------------------------------------------------
>>> >> > > > 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
>>> >> > >
>>> >> > >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > -----
>>> >> > Arnaud Héritier
>>> >> > http://aheritier.net
>>> >> > Mail/GTalk: aheritier AT gmail DOT com
>>> >> > Twitter/Skype : aheritier
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > -----
>>> > Arnaud Héritier
>>> > http://aheritier.net
>>> > Mail/GTalk: aheritier AT gmail DOT com
>>> > Twitter/Skype : aheritier
>>>
>>> ---------------------------------------------------------------------
>>> 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: Roadmap Proposal Plugin Releases
Posted by Anders Hammar <an...@hammar.net>.
ARCHETYPE-431 fixed.
However, when building I see a bunch of Maven "Build Failure" in the output
from tests. Don't know if that's expected, but it looks weird. The tests
pass though, but that could be wrong. Didn't have time to look into that.
Also, there are some warnings in the build that could be cleaned up.
/Anders
On Wed, Feb 4, 2015 at 3:43 PM, Anders Hammar <an...@hammar.net> wrote:
> I'll have a look.
>
> /Anders (mobile)
> Den 4 feb 2015 14:03 skrev "Benson Margulies" <bi...@gmail.com>:
>
> Gents, are you willing to do it and I'll just be RM?
>>
>>
>> On Wed, Feb 4, 2015 at 6:33 AM, Arnaud Héritier <ah...@gmail.com>
>> wrote:
>> > +1
>> >
>> > On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar <an...@hammar.net>
>> wrote:
>> >
>> >> > Ouch that's an old one :-)
>> >> >
>> >> > Yes I was interested to have a 2.3 release but we failed to find the
>> >> > motivation/time to close 431
>> >>
>> >>
>> >> Yes, I hardly even remember this one. The code seems to be fixed
>> except the
>> >> unit test. I'd say we should go for the easiest way so that we could
>> close
>> >> this ticket. Then we could create a new one for any remaining work.
>> >>
>> >> /Anders
>> >>
>> >>
>> >> >
>> >> > On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY <herve.boutemy@free.fr
>> >
>> >> > wrote:
>> >> >
>> >> > > I didn't work on this one for a long time
>> >> > >
>> >> > > Anders and Arnaud seem to have problems to decide how to fix and
>> close
>> >> > > http://jira.codehaus.org/browse/ARCHETYPE-431
>> >> > >
>> >> > > Regards,
>> >> > >
>> >> > > Hervé
>> >> > >
>> >> > > Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
>> >> > > > So, I've committed changes to the archetype system that I believe
>> >> > > > correspond to the 2.2.1 level. What else wants to happen before a
>> >> > > > release?
>> >> > > >
>> >> > > > On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <
>> herve.boutemy@free.fr
>> >> >
>> >> > > wrote:
>> >> > > > > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
>> >> > > > >> Hi,
>> >> > > > >>
>> >> > > > >> after some discussions at FOSDEM with Hervé, Kristian and
>> Robert
>> >> in
>> >> > > > >> Brussels i will summarize some ideas we would like to share
>> here:
>> >> > > > >>
>> >> > > > >> Make a final release of all plugins with minium Maven 2.2.1
>> >> > > > >> (prerequisites) and Java 1.5
>> >> > > > >>
>> >> > > > >> The current state of this approach can be watched on the
>> dist-tool
>> >> > [2]
>> >> > > > >
>> >> > > > > page.
>> >> > > > >
>> >> > > > >> After that we can start making releases of the plugins which
>> have
>> >> > > > >> minimum Maven 3.0 and JDK 6 (I think this will bring many
>> cleanups
>> >> > in
>> >> > > > >> code etc.)
>> >> > > > >>
>> >> > > > >> To make this more clear for the users the plugin versions
>> should
>> >> be
>> >> > > > >> bumped to 3.0....independant from their current version.
>> >> > > > >>
>> >> > > > >> This approach gives us the possibility to make in case of real
>> >> bugs
>> >> > > bug
>> >> > > > >> fix releases of the older plugins for JDK 5 etc. without
>> confusion
>> >> > JDK
>> >> > > > >> 5/JDK6 etc.
>> >> > > > >>
>> >> > > > >> These are the steps to leave Maven 2 completely behind..Yeah
>> ;-)
>> >> > > > >>
>> >> > > > >> Currently we have two (three) exceptions maven-site-plugin
>> (some
>> >> > kind
>> >> > > of
>> >> > > > >> special case), maven-scm-publish-plugin and maven-shade-plugin
>> >> which
>> >> > > > >> already have the Maven 3 requirement.
>> >> > > > >
>> >> > > > > more precisely, IMHO, we'll need to document 2 exceptions:
>> >> > > > > 1. plugins that are already at version 3.x but do not require
>> Maven
>> >> > 3:
>> >> > > > > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
>> >> > > > > maven-compiler-plugin 2. plugins that require Maven 3 with
>> version
>> >> <
>> >> > > 3.0:
>> >> > > > > maven-scm-publish-plugin and maven-shade-plugin
>> >> > > > >
>> >> > > > > And we'll need to add a documentation in every plugin that
>> changes
>> >> > its
>> >> > > > > requirements to remember to end-users which is the last version
>> >> that
>> >> > > > > requires Maven 2
>> >> > > > > Perhaps something to add to maven-docck-plugin
>> >> > > > >
>> >> > > > > Regards,
>> >> > > > >
>> >> > > > > Hervé
>> >> > > > >
>> >> > > > >> [1]
>> >> > http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
>> >> > > > >> [2]
>> >> > > > >>
>> >> > >
>> >> >
>> >>
>> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
>> >> > > > >> es. html
>> >> > > > >>
>> >> > > > >>
>> >> > > > >> Kind regards
>> >> > > > >> Karl Heinz Marbaise
>> >> > > > >>
>> >> > > > >>
>> >> > ---------------------------------------------------------------------
>> >> > > > >> 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
>> >> > > >
>> >> > > >
>> ---------------------------------------------------------------------
>> >> > > > 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
>> >> > >
>> >> > >
>> >> >
>> >> >
>> >> > --
>> >> > -----
>> >> > Arnaud Héritier
>> >> > http://aheritier.net
>> >> > Mail/GTalk: aheritier AT gmail DOT com
>> >> > Twitter/Skype : aheritier
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > -----
>> > Arnaud Héritier
>> > http://aheritier.net
>> > Mail/GTalk: aheritier AT gmail DOT com
>> > Twitter/Skype : aheritier
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
Re: Roadmap Proposal Plugin Releases
Posted by Anders Hammar <an...@hammar.net>.
I'll have a look.
/Anders (mobile)
Den 4 feb 2015 14:03 skrev "Benson Margulies" <bi...@gmail.com>:
> Gents, are you willing to do it and I'll just be RM?
>
>
> On Wed, Feb 4, 2015 at 6:33 AM, Arnaud Héritier <ah...@gmail.com>
> wrote:
> > +1
> >
> > On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar <an...@hammar.net>
> wrote:
> >
> >> > Ouch that's an old one :-)
> >> >
> >> > Yes I was interested to have a 2.3 release but we failed to find the
> >> > motivation/time to close 431
> >>
> >>
> >> Yes, I hardly even remember this one. The code seems to be fixed except
> the
> >> unit test. I'd say we should go for the easiest way so that we could
> close
> >> this ticket. Then we could create a new one for any remaining work.
> >>
> >> /Anders
> >>
> >>
> >> >
> >> > On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY <he...@free.fr>
> >> > wrote:
> >> >
> >> > > I didn't work on this one for a long time
> >> > >
> >> > > Anders and Arnaud seem to have problems to decide how to fix and
> close
> >> > > http://jira.codehaus.org/browse/ARCHETYPE-431
> >> > >
> >> > > Regards,
> >> > >
> >> > > Hervé
> >> > >
> >> > > Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
> >> > > > So, I've committed changes to the archetype system that I believe
> >> > > > correspond to the 2.2.1 level. What else wants to happen before a
> >> > > > release?
> >> > > >
> >> > > > On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <
> herve.boutemy@free.fr
> >> >
> >> > > wrote:
> >> > > > > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
> >> > > > >> Hi,
> >> > > > >>
> >> > > > >> after some discussions at FOSDEM with Hervé, Kristian and
> Robert
> >> in
> >> > > > >> Brussels i will summarize some ideas we would like to share
> here:
> >> > > > >>
> >> > > > >> Make a final release of all plugins with minium Maven 2.2.1
> >> > > > >> (prerequisites) and Java 1.5
> >> > > > >>
> >> > > > >> The current state of this approach can be watched on the
> dist-tool
> >> > [2]
> >> > > > >
> >> > > > > page.
> >> > > > >
> >> > > > >> After that we can start making releases of the plugins which
> have
> >> > > > >> minimum Maven 3.0 and JDK 6 (I think this will bring many
> cleanups
> >> > in
> >> > > > >> code etc.)
> >> > > > >>
> >> > > > >> To make this more clear for the users the plugin versions
> should
> >> be
> >> > > > >> bumped to 3.0....independant from their current version.
> >> > > > >>
> >> > > > >> This approach gives us the possibility to make in case of real
> >> bugs
> >> > > bug
> >> > > > >> fix releases of the older plugins for JDK 5 etc. without
> confusion
> >> > JDK
> >> > > > >> 5/JDK6 etc.
> >> > > > >>
> >> > > > >> These are the steps to leave Maven 2 completely behind..Yeah
> ;-)
> >> > > > >>
> >> > > > >> Currently we have two (three) exceptions maven-site-plugin
> (some
> >> > kind
> >> > > of
> >> > > > >> special case), maven-scm-publish-plugin and maven-shade-plugin
> >> which
> >> > > > >> already have the Maven 3 requirement.
> >> > > > >
> >> > > > > more precisely, IMHO, we'll need to document 2 exceptions:
> >> > > > > 1. plugins that are already at version 3.x but do not require
> Maven
> >> > 3:
> >> > > > > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
> >> > > > > maven-compiler-plugin 2. plugins that require Maven 3 with
> version
> >> <
> >> > > 3.0:
> >> > > > > maven-scm-publish-plugin and maven-shade-plugin
> >> > > > >
> >> > > > > And we'll need to add a documentation in every plugin that
> changes
> >> > its
> >> > > > > requirements to remember to end-users which is the last version
> >> that
> >> > > > > requires Maven 2
> >> > > > > Perhaps something to add to maven-docck-plugin
> >> > > > >
> >> > > > > Regards,
> >> > > > >
> >> > > > > Hervé
> >> > > > >
> >> > > > >> [1]
> >> > http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> >> > > > >> [2]
> >> > > > >>
> >> > >
> >> >
> >>
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
> >> > > > >> es. html
> >> > > > >>
> >> > > > >>
> >> > > > >> Kind regards
> >> > > > >> Karl Heinz Marbaise
> >> > > > >>
> >> > > > >>
> >> > ---------------------------------------------------------------------
> >> > > > >> 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
> >> > > >
> >> > > >
> ---------------------------------------------------------------------
> >> > > > 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
> >> > >
> >> > >
> >> >
> >> >
> >> > --
> >> > -----
> >> > Arnaud Héritier
> >> > http://aheritier.net
> >> > Mail/GTalk: aheritier AT gmail DOT com
> >> > Twitter/Skype : aheritier
> >> >
> >>
> >
> >
> >
> > --
> > -----
> > Arnaud Héritier
> > http://aheritier.net
> > Mail/GTalk: aheritier AT gmail DOT com
> > Twitter/Skype : aheritier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Roadmap Proposal Plugin Releases
Posted by Benson Margulies <bi...@gmail.com>.
Gents, are you willing to do it and I'll just be RM?
On Wed, Feb 4, 2015 at 6:33 AM, Arnaud Héritier <ah...@gmail.com> wrote:
> +1
>
> On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar <an...@hammar.net> wrote:
>
>> > Ouch that's an old one :-)
>> >
>> > Yes I was interested to have a 2.3 release but we failed to find the
>> > motivation/time to close 431
>>
>>
>> Yes, I hardly even remember this one. The code seems to be fixed except the
>> unit test. I'd say we should go for the easiest way so that we could close
>> this ticket. Then we could create a new one for any remaining work.
>>
>> /Anders
>>
>>
>> >
>> > On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY <he...@free.fr>
>> > wrote:
>> >
>> > > I didn't work on this one for a long time
>> > >
>> > > Anders and Arnaud seem to have problems to decide how to fix and close
>> > > http://jira.codehaus.org/browse/ARCHETYPE-431
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
>> > > > So, I've committed changes to the archetype system that I believe
>> > > > correspond to the 2.2.1 level. What else wants to happen before a
>> > > > release?
>> > > >
>> > > > On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <herve.boutemy@free.fr
>> >
>> > > wrote:
>> > > > > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
>> > > > >> Hi,
>> > > > >>
>> > > > >> after some discussions at FOSDEM with Hervé, Kristian and Robert
>> in
>> > > > >> Brussels i will summarize some ideas we would like to share here:
>> > > > >>
>> > > > >> Make a final release of all plugins with minium Maven 2.2.1
>> > > > >> (prerequisites) and Java 1.5
>> > > > >>
>> > > > >> The current state of this approach can be watched on the dist-tool
>> > [2]
>> > > > >
>> > > > > page.
>> > > > >
>> > > > >> After that we can start making releases of the plugins which have
>> > > > >> minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups
>> > in
>> > > > >> code etc.)
>> > > > >>
>> > > > >> To make this more clear for the users the plugin versions should
>> be
>> > > > >> bumped to 3.0....independant from their current version.
>> > > > >>
>> > > > >> This approach gives us the possibility to make in case of real
>> bugs
>> > > bug
>> > > > >> fix releases of the older plugins for JDK 5 etc. without confusion
>> > JDK
>> > > > >> 5/JDK6 etc.
>> > > > >>
>> > > > >> These are the steps to leave Maven 2 completely behind..Yeah ;-)
>> > > > >>
>> > > > >> Currently we have two (three) exceptions maven-site-plugin (some
>> > kind
>> > > of
>> > > > >> special case), maven-scm-publish-plugin and maven-shade-plugin
>> which
>> > > > >> already have the Maven 3 requirement.
>> > > > >
>> > > > > more precisely, IMHO, we'll need to document 2 exceptions:
>> > > > > 1. plugins that are already at version 3.x but do not require Maven
>> > 3:
>> > > > > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
>> > > > > maven-compiler-plugin 2. plugins that require Maven 3 with version
>> <
>> > > 3.0:
>> > > > > maven-scm-publish-plugin and maven-shade-plugin
>> > > > >
>> > > > > And we'll need to add a documentation in every plugin that changes
>> > its
>> > > > > requirements to remember to end-users which is the last version
>> that
>> > > > > requires Maven 2
>> > > > > Perhaps something to add to maven-docck-plugin
>> > > > >
>> > > > > Regards,
>> > > > >
>> > > > > Hervé
>> > > > >
>> > > > >> [1]
>> > http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
>> > > > >> [2]
>> > > > >>
>> > >
>> >
>> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
>> > > > >> es. html
>> > > > >>
>> > > > >>
>> > > > >> Kind regards
>> > > > >> Karl Heinz Marbaise
>> > > > >>
>> > > > >>
>> > ---------------------------------------------------------------------
>> > > > >> 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
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > 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
>> > >
>> > >
>> >
>> >
>> > --
>> > -----
>> > Arnaud Héritier
>> > http://aheritier.net
>> > Mail/GTalk: aheritier AT gmail DOT com
>> > Twitter/Skype : aheritier
>> >
>>
>
>
>
> --
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Roadmap Proposal Plugin Releases
Posted by Arnaud Héritier <ah...@gmail.com>.
+1
On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar <an...@hammar.net> wrote:
> > Ouch that's an old one :-)
> >
> > Yes I was interested to have a 2.3 release but we failed to find the
> > motivation/time to close 431
>
>
> Yes, I hardly even remember this one. The code seems to be fixed except the
> unit test. I'd say we should go for the easiest way so that we could close
> this ticket. Then we could create a new one for any remaining work.
>
> /Anders
>
>
> >
> > On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY <he...@free.fr>
> > wrote:
> >
> > > I didn't work on this one for a long time
> > >
> > > Anders and Arnaud seem to have problems to decide how to fix and close
> > > http://jira.codehaus.org/browse/ARCHETYPE-431
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
> > > > So, I've committed changes to the archetype system that I believe
> > > > correspond to the 2.2.1 level. What else wants to happen before a
> > > > release?
> > > >
> > > > On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <herve.boutemy@free.fr
> >
> > > wrote:
> > > > > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
> > > > >> Hi,
> > > > >>
> > > > >> after some discussions at FOSDEM with Hervé, Kristian and Robert
> in
> > > > >> Brussels i will summarize some ideas we would like to share here:
> > > > >>
> > > > >> Make a final release of all plugins with minium Maven 2.2.1
> > > > >> (prerequisites) and Java 1.5
> > > > >>
> > > > >> The current state of this approach can be watched on the dist-tool
> > [2]
> > > > >
> > > > > page.
> > > > >
> > > > >> After that we can start making releases of the plugins which have
> > > > >> minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups
> > in
> > > > >> code etc.)
> > > > >>
> > > > >> To make this more clear for the users the plugin versions should
> be
> > > > >> bumped to 3.0....independant from their current version.
> > > > >>
> > > > >> This approach gives us the possibility to make in case of real
> bugs
> > > bug
> > > > >> fix releases of the older plugins for JDK 5 etc. without confusion
> > JDK
> > > > >> 5/JDK6 etc.
> > > > >>
> > > > >> These are the steps to leave Maven 2 completely behind..Yeah ;-)
> > > > >>
> > > > >> Currently we have two (three) exceptions maven-site-plugin (some
> > kind
> > > of
> > > > >> special case), maven-scm-publish-plugin and maven-shade-plugin
> which
> > > > >> already have the Maven 3 requirement.
> > > > >
> > > > > more precisely, IMHO, we'll need to document 2 exceptions:
> > > > > 1. plugins that are already at version 3.x but do not require Maven
> > 3:
> > > > > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
> > > > > maven-compiler-plugin 2. plugins that require Maven 3 with version
> <
> > > 3.0:
> > > > > maven-scm-publish-plugin and maven-shade-plugin
> > > > >
> > > > > And we'll need to add a documentation in every plugin that changes
> > its
> > > > > requirements to remember to end-users which is the last version
> that
> > > > > requires Maven 2
> > > > > Perhaps something to add to maven-docck-plugin
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > >> [1]
> > http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> > > > >> [2]
> > > > >>
> > >
> >
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
> > > > >> es. html
> > > > >>
> > > > >>
> > > > >> Kind regards
> > > > >> Karl Heinz Marbaise
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> 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
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> >
> > --
> > -----
> > Arnaud Héritier
> > http://aheritier.net
> > Mail/GTalk: aheritier AT gmail DOT com
> > Twitter/Skype : aheritier
> >
>
--
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Re: Roadmap Proposal Plugin Releases
Posted by Anders Hammar <an...@hammar.net>.
> Ouch that's an old one :-)
>
> Yes I was interested to have a 2.3 release but we failed to find the
> motivation/time to close 431
Yes, I hardly even remember this one. The code seems to be fixed except the
unit test. I'd say we should go for the easiest way so that we could close
this ticket. Then we could create a new one for any remaining work.
/Anders
>
> On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY <he...@free.fr>
> wrote:
>
> > I didn't work on this one for a long time
> >
> > Anders and Arnaud seem to have problems to decide how to fix and close
> > http://jira.codehaus.org/browse/ARCHETYPE-431
> >
> > Regards,
> >
> > Hervé
> >
> > Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
> > > So, I've committed changes to the archetype system that I believe
> > > correspond to the 2.2.1 level. What else wants to happen before a
> > > release?
> > >
> > > On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <he...@free.fr>
> > wrote:
> > > > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
> > > >> Hi,
> > > >>
> > > >> after some discussions at FOSDEM with Hervé, Kristian and Robert in
> > > >> Brussels i will summarize some ideas we would like to share here:
> > > >>
> > > >> Make a final release of all plugins with minium Maven 2.2.1
> > > >> (prerequisites) and Java 1.5
> > > >>
> > > >> The current state of this approach can be watched on the dist-tool
> [2]
> > > >
> > > > page.
> > > >
> > > >> After that we can start making releases of the plugins which have
> > > >> minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups
> in
> > > >> code etc.)
> > > >>
> > > >> To make this more clear for the users the plugin versions should be
> > > >> bumped to 3.0....independant from their current version.
> > > >>
> > > >> This approach gives us the possibility to make in case of real bugs
> > bug
> > > >> fix releases of the older plugins for JDK 5 etc. without confusion
> JDK
> > > >> 5/JDK6 etc.
> > > >>
> > > >> These are the steps to leave Maven 2 completely behind..Yeah ;-)
> > > >>
> > > >> Currently we have two (three) exceptions maven-site-plugin (some
> kind
> > of
> > > >> special case), maven-scm-publish-plugin and maven-shade-plugin which
> > > >> already have the Maven 3 requirement.
> > > >
> > > > more precisely, IMHO, we'll need to document 2 exceptions:
> > > > 1. plugins that are already at version 3.x but do not require Maven
> 3:
> > > > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
> > > > maven-compiler-plugin 2. plugins that require Maven 3 with version <
> > 3.0:
> > > > maven-scm-publish-plugin and maven-shade-plugin
> > > >
> > > > And we'll need to add a documentation in every plugin that changes
> its
> > > > requirements to remember to end-users which is the last version that
> > > > requires Maven 2
> > > > Perhaps something to add to maven-docck-plugin
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > >> [1]
> http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> > > >> [2]
> > > >>
> >
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
> > > >> es. html
> > > >>
> > > >>
> > > >> Kind regards
> > > >> Karl Heinz Marbaise
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> 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
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
Re: Roadmap Proposal Plugin Releases
Posted by Arnaud Héritier <ah...@gmail.com>.
Ouch that's an old one :-)
Yes I was interested to have a 2.3 release but we failed to find the
motivation/time to close 431
On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY <he...@free.fr> wrote:
> I didn't work on this one for a long time
>
> Anders and Arnaud seem to have problems to decide how to fix and close
> http://jira.codehaus.org/browse/ARCHETYPE-431
>
> Regards,
>
> Hervé
>
> Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
> > So, I've committed changes to the archetype system that I believe
> > correspond to the 2.2.1 level. What else wants to happen before a
> > release?
> >
> > On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <he...@free.fr>
> wrote:
> > > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
> > >> Hi,
> > >>
> > >> after some discussions at FOSDEM with Hervé, Kristian and Robert in
> > >> Brussels i will summarize some ideas we would like to share here:
> > >>
> > >> Make a final release of all plugins with minium Maven 2.2.1
> > >> (prerequisites) and Java 1.5
> > >>
> > >> The current state of this approach can be watched on the dist-tool [2]
> > >
> > > page.
> > >
> > >> After that we can start making releases of the plugins which have
> > >> minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups in
> > >> code etc.)
> > >>
> > >> To make this more clear for the users the plugin versions should be
> > >> bumped to 3.0....independant from their current version.
> > >>
> > >> This approach gives us the possibility to make in case of real bugs
> bug
> > >> fix releases of the older plugins for JDK 5 etc. without confusion JDK
> > >> 5/JDK6 etc.
> > >>
> > >> These are the steps to leave Maven 2 completely behind..Yeah ;-)
> > >>
> > >> Currently we have two (three) exceptions maven-site-plugin (some kind
> of
> > >> special case), maven-scm-publish-plugin and maven-shade-plugin which
> > >> already have the Maven 3 requirement.
> > >
> > > more precisely, IMHO, we'll need to document 2 exceptions:
> > > 1. plugins that are already at version 3.x but do not require Maven 3:
> > > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
> > > maven-compiler-plugin 2. plugins that require Maven 3 with version <
> 3.0:
> > > maven-scm-publish-plugin and maven-shade-plugin
> > >
> > > And we'll need to add a documentation in every plugin that changes its
> > > requirements to remember to end-users which is the last version that
> > > requires Maven 2
> > > Perhaps something to add to maven-docck-plugin
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > >> [1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> > >> [2]
> > >>
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
> > >> es. html
> > >>
> > >>
> > >> Kind regards
> > >> Karl Heinz Marbaise
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Re: Roadmap Proposal Plugin Releases
Posted by Hervé BOUTEMY <he...@free.fr>.
I didn't work on this one for a long time
Anders and Arnaud seem to have problems to decide how to fix and close
http://jira.codehaus.org/browse/ARCHETYPE-431
Regards,
Hervé
Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit :
> So, I've committed changes to the archetype system that I believe
> correspond to the 2.2.1 level. What else wants to happen before a
> release?
>
> On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
> >> Hi,
> >>
> >> after some discussions at FOSDEM with Hervé, Kristian and Robert in
> >> Brussels i will summarize some ideas we would like to share here:
> >>
> >> Make a final release of all plugins with minium Maven 2.2.1
> >> (prerequisites) and Java 1.5
> >>
> >> The current state of this approach can be watched on the dist-tool [2]
> >
> > page.
> >
> >> After that we can start making releases of the plugins which have
> >> minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups in
> >> code etc.)
> >>
> >> To make this more clear for the users the plugin versions should be
> >> bumped to 3.0....independant from their current version.
> >>
> >> This approach gives us the possibility to make in case of real bugs bug
> >> fix releases of the older plugins for JDK 5 etc. without confusion JDK
> >> 5/JDK6 etc.
> >>
> >> These are the steps to leave Maven 2 completely behind..Yeah ;-)
> >>
> >> Currently we have two (three) exceptions maven-site-plugin (some kind of
> >> special case), maven-scm-publish-plugin and maven-shade-plugin which
> >> already have the Maven 3 requirement.
> >
> > more precisely, IMHO, we'll need to document 2 exceptions:
> > 1. plugins that are already at version 3.x but do not require Maven 3:
> > maven- site-plugin, maven-plugin-plugin, maven-pmd-plugin,
> > maven-compiler-plugin 2. plugins that require Maven 3 with version < 3.0:
> > maven-scm-publish-plugin and maven-shade-plugin
> >
> > And we'll need to add a documentation in every plugin that changes its
> > requirements to remember to end-users which is the last version that
> > requires Maven 2
> > Perhaps something to add to maven-docck-plugin
> >
> > Regards,
> >
> > Hervé
> >
> >> [1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> >> [2]
> >> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisit
> >> es. html
> >>
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
> ---------------------------------------------------------------------
> 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: Roadmap Proposal Plugin Releases
Posted by Benson Margulies <bi...@gmail.com>.
So, I've committed changes to the archetype system that I believe
correspond to the 2.2.1 level. What else wants to happen before a
release?
On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
>> Hi,
>>
>> after some discussions at FOSDEM with Hervé, Kristian and Robert in
>> Brussels i will summarize some ideas we would like to share here:
>>
>> Make a final release of all plugins with minium Maven 2.2.1
>> (prerequisites) and Java 1.5
>>
>> The current state of this approach can be watched on the dist-tool [2]
> page.
>>
>> After that we can start making releases of the plugins which have
>> minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups in
>> code etc.)
>>
>> To make this more clear for the users the plugin versions should be
>> bumped to 3.0....independant from their current version.
>>
>> This approach gives us the possibility to make in case of real bugs bug
>> fix releases of the older plugins for JDK 5 etc. without confusion JDK
>> 5/JDK6 etc.
>>
>> These are the steps to leave Maven 2 completely behind..Yeah ;-)
>>
>> Currently we have two (three) exceptions maven-site-plugin (some kind of
>> special case), maven-scm-publish-plugin and maven-shade-plugin which
>> already have the Maven 3 requirement.
> more precisely, IMHO, we'll need to document 2 exceptions:
> 1. plugins that are already at version 3.x but do not require Maven 3: maven-
> site-plugin, maven-plugin-plugin, maven-pmd-plugin, maven-compiler-plugin
> 2. plugins that require Maven 3 with version < 3.0: maven-scm-publish-plugin
> and maven-shade-plugin
>
> And we'll need to add a documentation in every plugin that changes its
> requirements to remember to end-users which is the last version that requires
> Maven 2
> Perhaps something to add to maven-docck-plugin
>
> Regards,
>
> Hervé
>
>>
>>
>> [1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
>> [2]
>> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.
>> html
>>
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Roadmap Proposal Plugin Releases
Posted by Hervé BOUTEMY <he...@free.fr>.
Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit :
> Hi,
>
> after some discussions at FOSDEM with Hervé, Kristian and Robert in
> Brussels i will summarize some ideas we would like to share here:
>
> Make a final release of all plugins with minium Maven 2.2.1
> (prerequisites) and Java 1.5
>
> The current state of this approach can be watched on the dist-tool [2]
page.
>
> After that we can start making releases of the plugins which have
> minimum Maven 3.0 and JDK 6 (I think this will bring many cleanups in
> code etc.)
>
> To make this more clear for the users the plugin versions should be
> bumped to 3.0....independant from their current version.
>
> This approach gives us the possibility to make in case of real bugs bug
> fix releases of the older plugins for JDK 5 etc. without confusion JDK
> 5/JDK6 etc.
>
> These are the steps to leave Maven 2 completely behind..Yeah ;-)
>
> Currently we have two (three) exceptions maven-site-plugin (some kind of
> special case), maven-scm-publish-plugin and maven-shade-plugin which
> already have the Maven 3 requirement.
more precisely, IMHO, we'll need to document 2 exceptions:
1. plugins that are already at version 3.x but do not require Maven 3: maven-
site-plugin, maven-plugin-plugin, maven-pmd-plugin, maven-compiler-plugin
2. plugins that require Maven 3 with version < 3.0: maven-scm-publish-plugin
and maven-shade-plugin
And we'll need to add a documentation in every plugin that changes its
requirements to remember to end-users which is the last version that requires
Maven 2
Perhaps something to add to maven-docck-plugin
Regards,
Hervé
>
>
> [1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> [2]
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.
> html
>
>
> Kind regards
> Karl Heinz Marbaise
>
> ---------------------------------------------------------------------
> 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: Roadmap Proposal Plugin Releases
Posted by Dennis Lundberg <de...@apache.org>.
On Mon, Feb 2, 2015 at 12:42 PM, Karl Heinz Marbaise <kh...@gmx.de> wrote:
> Hi,
>
> after some discussions at FOSDEM with Hervé, Kristian and Robert in Brussels
> i will summarize some ideas we would like to share here:
>
> Make a final release of all plugins with minium Maven 2.2.1 (prerequisites)
> and Java 1.5
>
> The current state of this approach can be watched on the dist-tool [2] page.
>
> After that we can start making releases of the plugins which have minimum
> Maven 3.0 and JDK 6 (I think this will bring many cleanups in code etc.)
I have documented the steps required to update a plugin/shared
component to Java 6 here
http://maven.apache.org/developers/java6.html
> To make this more clear for the users the plugin versions should be bumped
> to 3.0....independant from their current version.
I think we also need a versioning guide for plugins/components to
cover stuff like this. That page could also cover Semver, see separate
thread for that.
> This approach gives us the possibility to make in case of real bugs bug fix
> releases of the older plugins for JDK 5 etc. without confusion JDK 5/JDK6
> etc.
>
> These are the steps to leave Maven 2 completely behind..Yeah ;-)
>
> Currently we have two (three) exceptions maven-site-plugin (some kind of
> special case), maven-scm-publish-plugin and maven-shade-plugin which already
> have the Maven 3 requirement.
>
>
> [1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> [2]
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html
>
>
> Kind regards
> Karl Heinz Marbaise
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Roadmap Proposal Plugin Releases
Posted by Anders Hammar <an...@hammar.net>.
Sounds good to me. I especially like the Maven 3.0 (not 3.0.5) requirement.
/Anders
On Mon, Feb 2, 2015 at 12:42 PM, Karl Heinz Marbaise <kh...@gmx.de>
wrote:
> Hi,
>
> after some discussions at FOSDEM with Hervé, Kristian and Robert in
> Brussels i will summarize some ideas we would like to share here:
>
> Make a final release of all plugins with minium Maven 2.2.1
> (prerequisites) and Java 1.5
>
> The current state of this approach can be watched on the dist-tool [2]
> page.
>
> After that we can start making releases of the plugins which have minimum
> Maven 3.0 and JDK 6 (I think this will bring many cleanups in code etc.)
>
> To make this more clear for the users the plugin versions should be bumped
> to 3.0....independant from their current version.
>
> This approach gives us the possibility to make in case of real bugs bug
> fix releases of the older plugins for JDK 5 etc. without confusion JDK
> 5/JDK6 etc.
>
> These are the steps to leave Maven 2 completely behind..Yeah ;-)
>
> Currently we have two (three) exceptions maven-site-plugin (some kind of
> special case), maven-scm-publish-plugin and maven-shade-plugin which
> already have the Maven 3 requirement.
>
>
> [1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html
> [2] https://builds.apache.org/job/dist-tool-plugin/site/dist-
> tool-prerequisites.html
>
>
> Kind regards
> Karl Heinz Marbaise
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>