Re: Message typo

2016-01-20 Thread Paul Benedict 
I think this must be a logger issue. The entire message is actually this:
"[options] bootstrap class path not set in conjunction with -source 1.7"

So the logger must be cutting into the beginning of the string with
"[WARN]" plus any whitespace padding.

Cheers,
Paul

On Wed, Jan 20, 2016 at 12:03 PM, Andreas Gudian 
wrote:

> The message itself originates from the compiler (javac). No idea why it's
> truncated, though... ;-)
>
> 2016-01-20 6:18 GMT+01:00 Gary Gregory :
>
> > I'm not sure who output this message but there is obviously a etter
> issing:
> >
> > [INFO] -
> > [WARN] COMPILATION WARNING :
> > [INFO] -
> > [WARN] ootstrap class path not set in conjunction with -source 1.7
> >
> > Gary
> >
> > --
> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > Java Persistence with Hibernate, Second Edition
> > 
> > JUnit in Action, Second Edition 
> > Spring Batch in Action 
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>

[ANN] Apache Maven Compiler Plugin Version 3.5 Released

2016-01-20 Thread Andreas Gudian 
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.5.

The Compiler Plugin is used to compile the sources of your project.

http://maven.apache.org/plugins/maven-compiler-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-compiler-plugin
  3.5


Attention: Starting with this version, the maven-compiler-plugin requires
Maven 3 and won't work with Maven 2 anymore.


Release Notes - Maven Compiler Plugin - Version 3.5

** New Feature
* [MCOMPILER-203] - Allow compiler-plugin to specify annotation
processor dependencies

** Bug
* [MCOMPILER-211] - Compiler plugin (3.x) fails in eclipse

** Improvement
* [MCOMPILER-257] - Require Maven 3.0
* [MCOMPILER-258] - Removing exclusions from maven-core
* [MCOMPILER-259] - Upgrade maven-shared-utils to 3.0.0


Enjoy,

-The Apache Maven team

Re: Message typo

2016-01-20 Thread Andreas Gudian 
The message itself originates from the compiler (javac). No idea why it's
truncated, though... ;-)

2016-01-20 6:18 GMT+01:00 Gary Gregory :

> I'm not sure who output this message but there is obviously a etter issing:
>
> [INFO] -
> [WARN] COMPILATION WARNING :
> [INFO] -
> [WARN] ootstrap class path not set in conjunction with -source 1.7
>
> Gary
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

CD versioning

2016-01-20 Thread Benson Margulies 
Some time ago, I recall some email about dynamic versioning; the idea
being that all the  elements in all the POMs of the project
would look like ${version}, and a jar dropped into
the maven extensions directory would provide a component that would
generate the version, perhaps from a git hash or something like that.
Is there any doc around on how to set this up? Is it functional in
3.2.5?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org