You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benson Margulies <bi...@gmail.com> on 2011/07/03 02:04:18 UTC
compiler plugin config in plugins -- recent parent change seems ineffectual
OK, well, I'm stumped.
In maven-shade-plugin, I modified my local copy to point to
maven-plugins version 20 as parent. This in turn points to maven
parent 20. Which configures the compiler plugin for source level 1.5.
Yet, help:effective-pom shows me source level 1.4, and adding in a
generic gets an error.
Now, I can add the compiler plugin to the shade pom, but I'd like to
understand what I'm missing here.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: compiler plugin config in plugins -- recent parent change seems ineffectual
Posted by Benson Margulies <bi...@gmail.com>.
correction: I made shade point to maven-plugins:21, which in turn
points to maven-parent 20, which is the one with the 1.5's in it.
On Sat, Jul 2, 2011 at 8:04 PM, Benson Margulies <bi...@gmail.com> wrote:
> OK, well, I'm stumped.
>
> In maven-shade-plugin, I modified my local copy to point to
> maven-plugins version 20 as parent. This in turn points to maven
> parent 20. Which configures the compiler plugin for source level 1.5.
>
> Yet, help:effective-pom shows me source level 1.4, and adding in a
> generic gets an error.
>
> Now, I can add the compiler plugin to the shade pom, but I'd like to
> understand what I'm missing here.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: compiler plugin config in plugins -- recent parent change seems ineffectual
Posted by Hervé BOUTEMY <he...@free.fr>.
yes, MPOM-13
:)
Le dimanche 3 juillet 2011, Benson Margulies a écrit :
> Oh, Duh, I see. It's only in a profile in the plugin parent. oops.
>
> On Sat, Jul 2, 2011 at 8:04 PM, Benson Margulies <bi...@gmail.com>
wrote:
> > OK, well, I'm stumped.
> >
> > In maven-shade-plugin, I modified my local copy to point to
> > maven-plugins version 20 as parent. This in turn points to maven
> > parent 20. Which configures the compiler plugin for source level 1.5.
> >
> > Yet, help:effective-pom shows me source level 1.4, and adding in a
> > generic gets an error.
> >
> > Now, I can add the compiler plugin to the shade pom, but I'd like to
> > understand what I'm missing here.
>
> ---------------------------------------------------------------------
> 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: compiler plugin config in plugins -- recent parent change seems ineffectual
Posted by Benson Margulies <bi...@gmail.com>.
Oh, Duh, I see. It's only in a profile in the plugin parent. oops.
On Sat, Jul 2, 2011 at 8:04 PM, Benson Margulies <bi...@gmail.com> wrote:
> OK, well, I'm stumped.
>
> In maven-shade-plugin, I modified my local copy to point to
> maven-plugins version 20 as parent. This in turn points to maven
> parent 20. Which configures the compiler plugin for source level 1.5.
>
> Yet, help:effective-pom shows me source level 1.4, and adding in a
> generic gets an error.
>
> Now, I can add the compiler plugin to the shade pom, but I'd like to
> understand what I'm missing here.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org