maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mirko Friedenhagen <mfriedenha...@gmail.com>
Subject Property namespaces Was: Changing JDK version without specifying maven-compiler-plugin version
Date Wed, 27 Nov 2013 06:49:43 GMT
Hello Laird,

the only pity with using properties is that they are not namespaced most of
the time (the maven.compiler.* ones being an exception here), "output" is
claimed at least by three mojos IIRC. And skipTests is almost a general one
but you may not easily specify that you do not want to run surefire but
e.g. invoker tests nonetheless :-)

I would have liked conventions like always "prefix with plugin name".

Regards Mirko
-- 
Sent from my mobile
On Nov 27, 2013 1:48 AM, "Laird Nelson" <ljnelson@gmail.com> wrote:

> On Tuesday, November 26, 2013, Malte Skoruppa wrote:
> >
> > is there some way for me to achieve the following three things at the
> same
> > time:
> > (1) have Maven compile my source files with -source 1.4 (or anything
> > higher than 1.3)
> > (2) *not* specify the maven-compiler-plugin version to use; instead, have
> > Maven dynamically use the latest one available;
> > (3) *not* have Maven bitch about my project being "malformed" ;-)
>
>
> Yes.  In your pom.xml's <properties> section add this:
>
> <maven.compiler.source>1.6</maven.compiler.source>
> <maven.compiler.target>1.6</maven.compiler.target>
>
> No other configuration or verbiage needed.
>
> All of the other posters' words are good. But no one answered your
> question.
>
> Best,
> Laird
>
>
> --
> http://about.me/lairdnelson
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message