Not sure I follow, but I'm just saying that don't up the 'prerequisites'
element unless there is a real reason. That element also controls which
Maven versions that can USE the plugin. If you want to ensure/force a
specific minimum for building just use the enforce-plugin.
/Anders
On Thu, Oct 8, 2015 at 9:29 AM, Tibor Digana <tibor.dig...@googlemail.com>
wrote:
> Hi Anders,
>
> Sorry for that, you wasn't in our internal discussion in December 2014 or
> November where we agreed to release experimental API in 2.x, and 3.0.
> I think I can release the new API in last 2.20 this year and I will listen
> to impression from our Maven Users.
> We already have the API in a branch but it needs some work to extend with
> maybe Maven JSR330 injections - needs new discussion.
> When everything would be fine we will simply release 3.0 which would be a
> change of JDK and fixes required from Users group.
>
>
>
> On Thu, Oct 8, 2015 at 9:04 AM, Anders Hammar <and...@hammar.net> wrote:
>
> > Why 3.0.5?
> >
> > We've had this discussion (in general for plugins) before and IIRC we
> > decided on 3.0.
> >
> > /Anders
> >
> > On Thu, Oct 8, 2015 at 8:43 AM, Tibor Digana <tibordig...@apache.org>
> > wrote:
> >
> > > Do you agree to specify these build requirements in surefire POM?
> > >
> > > <prerequisites>
> > > <maven>3.0.5</maven>
> > > </prerequisites>
> > >
> > > Updating README.txt in GitHub.
> > >
> > > Adding configuration of maven-enforcer-plugin with
> > > requireMavenVersion=[3.0.5,)
> > >
> > > and removing in every POM:
> > >
> > > <prerequisites>
> > > <maven>${mavenVersion}</maven>
> > > </prerequisites>
> > >
> > > Configuring maven-plugin-plugin:
> > >
> > > <requirements>
> > > <maven>2.2.1</maven>
> > > <jdk>1.5</jdk>
> > > </requirements>
> > >
> > > I will run mvn site site:stage and I will check if every report
> > > has Maven requirements specifying Version 2.2.1.
> > >
> >
>
>
>
> --
> Cheers
> Tibor
>
