Re: [ANN] Apache Maven Compiler Plugin Version 3.5 Released

2016-01-21 Thread Andrei Ivanov 
Hi,
Thank you for your work :-)

I just wished the long standing
https://issues.apache.org/jira/browse/MCOMPILER-209 would have been
included too :-(


On Wed, Jan 20, 2016 at 9:43 PM, Andreas Gudian  wrote:

> 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: [ANN] Apache Maven Compiler Plugin Version 3.5 Released

2016-01-21 Thread Thomas Broyer 
On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian  wrote:

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

Great! But…

I don't get how you can add a feature about annotation processors and not
at the same time fix one of the most annoying issue when using annotation
processors that generate Java sources:
https://issues.apache.org/jira/browse/MCOMPILER-235

Is everyone always doing clean builds? or everyone sets
useIncrementalCompilation to false?
(or maybe everyone actually still uses 3.1; along with the
build-helper-maven-plugin if they need the generated sources added as
source roots in downstream plugins)

/me frustrated

Re: CD versioning

2016-01-21 Thread Benson Margulies 
On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise  wrote:
> Hi Benson,
>
> you know that you can define the following properties since Maven 3.2.1[1]
>
> ${revision}, ${changelist} and ${sha1} which can be set outside from Maven
> via:
>
> mvn -Drevision=1.2.3-SNAPSHOT ...
>
> and you can use it:
>
> 
>   ...
>   ...
>   ${revision}
> ..
> 
>
> in case of a multi module build you can also use it in the parent definition
> of the children...
>
>
> but there does not exist some kind of jar which generates the version...as
> far as i know...

that's the disconnect; i thought that JvZ or someone described a
drop-in Jar that could cause a property to come into existence (which
could then be referenced). Of course, I can wrap a script around mvn
if there is no such beast.


>
> Kind regards
> Karl Heinz Marbaise
>
> [1]: http://maven.apache.org/docs/3.2.1/release-notes.html
>
> On 1/20/16 1:11 PM, Benson Margulies wrote:
>>
>> 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
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

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

Fwd: [ANN] Apache Maven Compiler Plugin Version 3.5 Released

2016-01-21 Thread Andreas Gudian 
cross-posting to the users-list...

-- Forwarded message --
From: Andreas Gudian 
Date: 2016-01-21 20:49 GMT+01:00
Subject: Re: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
To: Maven Developers List 


I've just committed a potential fix for MCOMPILER-235.

If some of you could use 3.6-SNAPSHOT (either build it yourself with my
commit included, or wait a bit until it's updated in the apache snapshots
repository) and see if it works for you, I'd apreciate it.

But let's continue that discussion in
https://issues.apache.org/jira/browse/MCOMPILER-235

Thanks,
Andreas


2016-01-21 20:44 GMT+01:00 Andreas Gudian :

> To be honest, I wasn't even aware of that bug, as I only checked the
> summaries of the x latest bugs shortly before the release. And yes, when on
> the command line, I always do a clean build, whereas my IDE does the
> incremental stuff corrctly... :-/
>
> But I get that it's annoying and I'll look into it.
>
> Andreas
>
> 2016-01-21 15:44 GMT+01:00 Thomas Broyer :
>
>> On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian 
>> wrote:
>>
>> > ** New Feature
>> > * [MCOMPILER-203] - Allow compiler-plugin to specify annotation
>> > processor dependencies
>> >
>>
>> Great! But…
>>
>> I don't get how you can add a feature about annotation processors and not
>> at the same time fix one of the most annoying issue when using annotation
>> processors that generate Java sources:
>> https://issues.apache.org/jira/browse/MCOMPILER-235
>>
>> Is everyone always doing clean builds? or everyone sets
>> useIncrementalCompilation to false?
>> (or maybe everyone actually still uses 3.1; along with the
>> build-helper-maven-plugin if they need the generated sources added as
>> source roots in downstream plugins)
>>
>> /me frustrated
>>
>
>

Re: iText 4.2.0 - Could a software licence be changed from MPL/LGPL to AGPL by simply redistributing the pom.xml?

2016-01-21 Thread Mirko Friedenhagen 
Hello Siegfried,

I do not think this was an accident, see
https://issues.sonatype.org/plugins/servlet/mobile#issue/MVNCENTRAL-760.

The relocation does break builds as the package is different as well. I am
not a lawyer but at I think it is not a nice move to cause breaking builds
and licensing issues two years after something is published.
Regards
Mirko
-- 
Sent from my mobile
Am 19.01.2016 23:58 schrieb "Siegfried Goeschl" :

> Hi folks,
>
> I have a simple simple question - is it possible/legal to change the
> software licence by simply re-distributing a POM a couple of years later?
>
> During a code review I came across a project using itext-4.2.0-jar.
>
> AFAIK iText 2.1.7 was the last version under MPL/LGPL and later they moved
> to AGPL V3 - I suggested to remove the library but the developer insisted
> that the library was indeed under MPL :-O
>
> * He showed me itext-4.2.0.jar/META-INF/maven/com.lowagie/itext/pom.xml
> clearly displaying a MPL/LGPL licence
> * I pointed him to
> http://search.maven.org/#artifactdetails%7Ccom.lowagie%7Citext%7C4.2.0%7Cpom
> clearly displaying a AGPL V3 licence
>
> But the
> http://search.maven.org/remotecontent?filepath=com/lowagie/itext/4.2.0/itext-4.2.0.pom
> actually contains a "relocation" section
>
> 
> 
> GNU Affero General Public License v3
> http://www.fsf.org/licensing/licenses/agpl-3.0.html
> 
> 
> 
> 
> com.itextpdf
> itextpdf
> 5.5.6
> After release 2.1.7, iText moved from the MPLicense to
> the AGPLicense.
> The groupId changed from com.lowagie to com.itextpdf and the
> artifactId from itext to itextpdf.
> See http://itextpdf.com/functionalitycomparison for more
> information.
> 
> 
>
> Mhmm, that puzzled me because itext-4.2.0.jar still has "com.lowagie"
> package name so I started digging through Maven Central
>
>
> 1) What Maven Central Says
> ===
>
> http://repo1.maven.org/maven2/com/lowagie/itext/4.2.0/
>
> itext-4.2.0-bundle.jar.asc 20-Sep-2012 16:34
>490
> itext-4.2.0-bundle.jar.asc.md5 20-Sep-2012 16:34
> 32
> itext-4.2.0-bundle.jar.asc.sha120-Sep-2012 16:34
> 40
> itext-4.2.0-javadoc.jar20-Sep-2012 16:34
>4498819
> itext-4.2.0-javadoc.jar.asc20-Sep-2012 16:34
>490
> itext-4.2.0-javadoc.jar.asc.md520-Sep-2012 16:34
> 32
> itext-4.2.0-javadoc.jar.asc.sha1   20-Sep-2012 16:34
> 40
> itext-4.2.0-javadoc.jar.md520-Sep-2012 16:34
> 32
> itext-4.2.0-javadoc.jar.sha1   20-Sep-2012 16:34
> 40
> itext-4.2.0-sources.jar20-Sep-2012 16:34
>4061295
> itext-4.2.0-sources.jar.asc20-Sep-2012 16:34
>490
> itext-4.2.0-sources.jar.asc.md520-Sep-2012 16:34
> 32
> itext-4.2.0-sources.jar.asc.sha1   20-Sep-2012 16:34
> 40
> itext-4.2.0-sources.jar.md520-Sep-2012 16:34
> 32
> itext-4.2.0-sources.jar.sha1   20-Sep-2012 16:34
> 40
> itext-4.2.0.jar20-Sep-2012 16:34
>2243043
> itext-4.2.0.jar.asc20-Sep-2012 16:34
>490
> itext-4.2.0.jar.asc.md520-Sep-2012 16:34
> 32
> itext-4.2.0.jar.asc.sha1   20-Sep-2012 16:34
> 40
> itext-4.2.0.jar.md520-Sep-2012 16:34
> 32
> itext-4.2.0.jar.sha1   20-Sep-2012 16:34
> 40
> itext-4.2.0.pom10-Jul-2015 08:16
>   2156
> itext-4.2.0.pom.asc10-Jul-2015 08:16
>821
> itext-4.2.0.pom.asc.md509-Jul-2015 12:33
> 32
> itext-4.2.0.pom.asc.sha1   09-Jul-2015 12:33
> 40
> itext-4.2.0.pom.md510-Jul-2015 08:16
> 32
> itext-4.2.0.pom.sha1   10-Jul-2015 08:16
> 40
>
> Interesting - the pom.xml was re-distributed a couple of months ago while
> the iText library is still from 2012. I guess the redistribution was caused
> by the additional "relocation" section of the pom.xml
>
> > wget
> http://repo1.maven.org/maven2/com/lowagie/itext/4.2.0/itext-4.2.0.jar
> > wget
> http://repo1.maven.org/maven2/com/lowagie/itext/4.2.0/itext-4.2.0.jar.asc
> > gpg --verify itext-4.2.0.jar.asc
>
> itext> gpg --verify itext-4.2.0.jar.asc
> gpg: assuming signed data in `itext-4.2.0.jar'
> gpg: Signature made Thu Sep 20 17:24:41 2012 CEST using

Re: CD versioning

2016-01-21 Thread Jason van Zyl 
I have something that I wouldn’t make public but you’re free to hack it up and 
do what you like with it.

> On Jan 21, 2016, at 11:47 AM, Benson Margulies  wrote:
> 
> On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise  
> wrote:
>> Hi Benson,
>> 
>> you know that you can define the following properties since Maven 3.2.1[1]
>> 
>> ${revision}, ${changelist} and ${sha1} which can be set outside from Maven
>> via:
>> 
>> mvn -Drevision=1.2.3-SNAPSHOT ...
>> 
>> and you can use it:
>> 
>> 
>>  ...
>>  ...
>>  ${revision}
>> ..
>> 
>> 
>> in case of a multi module build you can also use it in the parent definition
>> of the children...
>> 
>> 
>> but there does not exist some kind of jar which generates the version...as
>> far as i know...
> 
> that's the disconnect; i thought that JvZ or someone described a
> drop-in Jar that could cause a property to come into existence (which
> could then be referenced). Of course, I can wrap a script around mvn
> if there is no such beast.
> 
> 
>> 
>> Kind regards
>> Karl Heinz Marbaise
>> 
>> [1]: http://maven.apache.org/docs/3.2.1/release-notes.html
>> 
>> On 1/20/16 1:11 PM, Benson Margulies wrote:
>>> 
>>> 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
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-



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

Re: CD versioning

2016-01-21 Thread Karl Heinz Marbaise 

Hi Benson,

you know that you can define the following properties since Maven 3.2.1[1]

${revision}, ${changelist} and ${sha1} which can be set outside from 
Maven via:


mvn -Drevision=1.2.3-SNAPSHOT ...

and you can use it:


  ...
  ...
  ${revision}
..


in case of a multi module build you can also use it in the parent 
definition of the children...



but there does not exist some kind of jar which generates the 
version...as far as i know...


Kind regards
Karl Heinz Marbaise

[1]: http://maven.apache.org/docs/3.2.1/release-notes.html

On 1/20/16 1:11 PM, Benson Margulies wrote:

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


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