On Tue, 14 Jan 2014 22:41:22 +0100
"Robert Scholte" <codeh...@sourcegrounds.com> wrote:
> I prefer a good latest mojo-parent over a restricted parent which could
> mean override these restrictions or fall back to an older version, just
> like Anders describes.
>
> So for now I think we should disable (=comment out) the
> RequirePrerequisite Rule until the packaging type can be controlled (we
> only want this for maven-plugin packaging) and let's see if exclusion of
> 2.1.x and 2.2.0 works. Also change the maven prerequisite to 2.0 (default)
> and keep the comments, they should explain quite clear how it is used (for
> future discussions)
>
> In general we'd like to keep the the prerequisite as low as possible for
> Maven plugins. However, I think we should gently start forcing users to
> move forward. The jump to 2.2.1 might be a bit too much. We could start a
> new thread on the users mailing-list about a suggestion for a proper
> version, let's say 2.0.6 or 2.0.9
I was about to send mylself a same email.
Welcome to jurassic park!
Hopefuly we don't maintain anymore maven 1.0 :)
I will drop the release, revert some stuff and reroll another release, since
there is the problem of site generation.
>
> thanks,
>
> Robert
>
>
> Op Sat, 11 Jan 2014 21:39:15 +0100 schreef Anders Hammar
> <and...@hammar.net>:
>
> >> Who says you need to use the latest parent anyways?
> >>
> >
> > I think the latest parent should be useable by all mojos (unless they are
> > VERY special). So introducing something we know prevents that isn't good
> > IMHO.
> >
> >
> >> And AFAIR you can override the enforcer rule if you want to use the
> >> latest
> >> parent anyway
> >>
> >
> > That would be a bad think I think, as it would require overriding the
> > execution by the id ('mojo-enforcer-rules'). Which would override all the
> > rules (not only the Maven version one), which would open up for future
> > issues if we later on add more rules in this execution that those mojos
> > wouldn't be using.
> > Remember, we add these rules for a reason.
> >
> > Sorry to turning this vote thread into a discussion, but I think that
> > fairly major thing sneaked in here. If we add this rule we should agree
> > on
> > that all future mojo version would required Maven 2.2.1+ (at least when
> > bumping minor/major, not bugfix). And we should probably also state this
> > clearly on the Mojo homepage.
> >
> > /Anders
> >
> >>
> >>
> >> On Friday, 10 January 2014, Anders Hammar wrote:
> >>
> >>> -1 (for now)
> >>>
> >>> Is this really what we want? No more mojo releases that supports Maven
> >>> pre-2.2.1 versions? I don't think so.
> >>>
> >>> From build:
> >>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (mojo-enforcer-rules) @
> >>> sqlj-maven-plugin ---
> >>> [WARNING] Rule 3: org.apache.maven.plugins.enforcer.RequirePrerequisite
> >>> failed with message:
> >>> The specified Maven prerequisite( 2.0 ) doesn't match the required
> >>> version: [2.2.1,)
> >>>
> >>>
> >>> /Anders
> >>>
> >>>
> >>> On Fri, Jan 10, 2014 at 10:08 PM, Tony Chemit
> >>> <che...@codelutin.com>wrote:
> >>>
> >>>> On Fri, 10 Jan 2014 13:00:12 -0800
> >>>> Dan Tran <dant...@gmail.com> wrote:
> >>>>
> >>>> > I try to pickup the new parent with maven-native, and it seems i
> >>>> have
> >>>> to add
> >>>> >
> >>>> > <prerequisites>
> >>>> > <maven>2.2.1</maven>
> >>>> > </prerequisites>
> >>>> >
> >>>> >
> >>>> > to every single project. Is it correct?
> >>>>
> >>>> Yes this is it.
> >>>>
> >>>> >
> >>>> > -Dan
> >>>> >
> >>>> >
> >>>> >
> >>>> > On Fri, Jan 10, 2014 at 11:54 AM, Karl Heinz Marbaise <
> >>>> khmarba...@gmx.de>wrote:
> >>>> >
> >>>> > > Hi,
> >>>> > >
> >>>> > > +1 mojo-parent version 33
> >>>> > > +1 mojo-sandbox-parent version 14
> >>>> > >
> >>>> > > Kind Regards
> >>>> > > Karl Heinz Marbaise
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> ---------------------------------------------------------------------
> >>>> > > To unsubscribe from this list, please visit:
> >>>> > >
> >>>> > > http://xircles.codehaus.org/manage_email
> >>>> > >
> >>>> > >
> >>>> > >
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Tony Chemit
> >>>> --------------------
> >>>> tél: +33 (0) 2 40 50 29 28
> >>>> http://www.codelutin.com
> >>>> email: che...@codelutin.com
> >>>> twitter: https://twitter.com/tchemit
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe from this list, please visit:
> >>>>
> >>>> http://xircles.codehaus.org/manage_email
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >> --
> >> Sent from my phone
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
--
Tony Chemit
--------------------
tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
