You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Andreas Gudian <ag...@apache.org> on 2016/01/20 20:43:10 UTC
[ANN] Apache Maven Compiler Plugin Version 3.5 Released
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:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.5</version>
</plugin>
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
Fwd: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Andreas Gudian <an...@gmail.com>.
cross-posting to the users-list...
---------- Forwarded message ----------
From: Andreas Gudian <an...@gmail.com>
Date: 2016-01-21 20:49 GMT+01:00
Subject: Re: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
To: Maven Developers List <de...@maven.apache.org>
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 <an...@gmail.com>:
> 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 <t....@gmail.com>:
>
>> On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <ag...@apache.org>
>> 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: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Andreas Gudian <an...@gmail.com>.
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 <an...@gmail.com>:
> 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 <t....@gmail.com>:
>
>> On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <ag...@apache.org>
>> 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: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Andreas Gudian <an...@gmail.com>.
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 <t....@gmail.com>:
> On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <ag...@apache.org> 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: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Alexander Kriegisch <al...@kriegisch.name>.
Disclaimer: I just have my tablet here, I cannot actually do anything in Git or an IDE now.
Anyway, a little hint: I counted about 38 or so commits in between 3.1 and 3.2, i.e. with 'git bisect' (one of my favourite bug hunting tools) you should need max. 6 iterations in order to identify the exact commit which caused your current problem.
Regards
--
Alexander Kriegisch
http://scrum-master.de
> Am 21.01.2016 um 17:30 schrieb Tibor Digana <ti...@googlemail.com>:
>
> This issue must be really annoying to users, I agree.
> The way would be to find the exact commit in GitHub between Versions 3.1
> and 3.2 which caused this issue.
> This means compiling the maven-compiler-plugin in a loop and testing the
> project attached over and over again.
>
>> On Thu, Jan 21, 2016 at 3:44 PM, Thomas Broyer <t....@gmail.com> wrote:
>>
>>> On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <ag...@apache.org> 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
>>
>
>
>
> --
> Cheers
> Tibor
Re: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Tibor Digana <ti...@googlemail.com>.
This issue must be really annoying to users, I agree.
The way would be to find the exact commit in GitHub between Versions 3.1
and 3.2 which caused this issue.
This means compiling the maven-compiler-plugin in a loop and testing the
project attached over and over again.
On Thu, Jan 21, 2016 at 3:44 PM, Thomas Broyer <t....@gmail.com> wrote:
> On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <ag...@apache.org> 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
>
--
Cheers
Tibor
Re: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Thomas Broyer <t....@gmail.com>.
On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <ag...@apache.org> 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: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Andrei Ivanov <an...@gmail.com>.
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 <ag...@apache.org> 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:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.5</version>
> </plugin>
>
> 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
Posted by Thomas Broyer <t....@gmail.com>.
On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <ag...@apache.org> 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: [ANN] Apache Maven Compiler Plugin Version 3.5 Released
Posted by Andrei Ivanov <an...@gmail.com>.
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 <ag...@apache.org> 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:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.5</version>
> </plugin>
>
> 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
>