Re: Maven Compiler Plugin Release 3.7.1--

[Naman Nigam]

+1 (to know why is the release held)
Mostly a follower of this mailing list though, yet I can sense where this
is coming from and I do agree there are already a lot of fixes that 3.7.1
can come up with to solve for the community unless 3.8.0 is really really
near to release or we are not seeking many changes after 3.8.0 release
coming up in quick succession.


Regards
Naman Nigam
 +91-9761212401 | LinkedIn 


On Mon, Jul 23, 2018 at 1:55 PM Karl Heinz Marbaise 
wrote:

> Hi,
>
> I want to know if there are objections to make a new release of Maven
> Compiler Plugin cause it already has much fixes in there which seemed to
> be needed in the community..
>
> If have more fixes we should make another release afterwards..
>
> WDYT ?
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Maven Compiler Plugin Release 3.7.1--

[Karl Heinz Marbaise]

Hi,

I want to know if there are objections to make a new release of Maven 
Compiler Plugin cause it already has much fixes in there which seemed to 
be needed in the community..


If have more fixes we should make another release afterwards..

WDYT ?

Kind regards
Karl Heinz Marbaise

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

Re: maven-compiler-plugin release

[Robert Scholte]

I need to work an the plexus-java performance issue and also think of a  
way to preserve the extra JPMS arguments used during compilation so they  
can be available at runtime as well (= MCOMPILER-296).
As far as I know these are the final open issues required to have a  
complete Java 9 supported plugin.


I will pick these up probably next week.

thanks,
Robert


On Tue, 15 Aug 2017 22:34:19 +0200, Karl Heinz Marbaise  
 wrote:



Hi Robert,

would you think we should do another release for maven-compiler-plugin ?

Kind regards
Karl Heinz Marbaise


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

maven-compiler-plugin release

[Karl Heinz Marbaise]

Hi Robert,

would you think we should do another release for maven-compiler-plugin ?

Kind regards
Karl Heinz Marbaise

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

Re: Maven Compiler Plugin Release

[Karl Heinz Marbaise]

Hi,

so based that no one raised his hand i will continue and start the 
release within this week...


If you have objections or things which should be part of the release 
please raise a hand as soon as possible so i can hold on...


Kind regards
Karl Heinz Marbaise
On 3/15/15 11:41 PM, Karl Heinz Marbaise wrote:

Hi,

I just wan't to cut a release for maven-compiler-plugin version 3.3
within the next week

currently having only 4 issues solved there...Is there something else
which should be part of it?

I think this release would be the last Maven 2.2.1 supporting release...

Kind regards
Karl Heinz Marbaise


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

Maven Compiler Plugin Release

[Karl Heinz Marbaise]

Hi,

I just wan't to cut a release for maven-compiler-plugin version 3.3 
within the next week


currently having only 4 issues solved there...Is there something else 
which should be part of it?


I think this release would be the last Maven 2.2.1 supporting release...

Kind regards
Karl Heinz Marbaise

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

Re: Cutting another maven-compiler-plugin release to set the default source/target to 1.5

[Milos Kleint]

On Sat, Apr 10, 2010 at 12:57 PM, Benjamin Bentmann 
benjamin.bentm...@udo.edu wrote:

 Brett Porter wrote:

  [...] though for your purposes it might be more expedient to put the
 configuration in the 3.0 super POM?


 -1, it's unlucky when builds depend on the version of Maven being used,
 this should not be be the norm. Ideally, plugin behavior should only be a
 function of the plugin version and not also the Maven version.



I agree with benjamin here. Adittionally to what has been said,
configuration in maven superpom makes IDE embedded resolution a pain.

Milos




 Benjamin


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

Re: Cutting another maven-compiler-plugin release to set the default source/target to 1.5

[Benjamin Bentmann]

Brett Porter wrote:


[...] though for your purposes it might be more expedient to put the 
configuration in the 3.0 super POM?


-1, it's unlucky when builds depend on the version of Maven being used, 
this should not be be the norm. Ideally, plugin behavior should only be 
a function of the plugin version and not also the Maven version.



Benjamin

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

Cutting another maven-compiler-plugin release to set the default source/target to 1.5

[Jason van Zyl]

The defaults are currently set in the plexus-compiler-javac component (to 
source=1.3 and target=1.1) and not in the maven-compiler-plugin. I would just 
like to set the default in the AbstractCompilerMojo and be done with it. This 
way when we release 3.0-beta-1 the default source/target will be 1.5. I'll also 
bump the locked down version of the maven-compiler-plugin I cut accordingly.

If I don't hear anything I'll assume that's fine and cut it.

Thanks,

Jason

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

Re: Cutting another maven-compiler-plugin release to set the default source/target to 1.5

[Brett Porter]

This is the issue to update when you do:

http://jira.codehaus.org/browse/MCOMPILER-80

I agree it should be done, though for your purposes it might be more expedient 
to put the configuration in the 3.0 super POM?

- Brett

On 10/04/2010, at 10:58 AM, Jason van Zyl wrote:

 The defaults are currently set in the plexus-compiler-javac component (to 
 source=1.3 and target=1.1) and not in the maven-compiler-plugin. I would just 
 like to set the default in the AbstractCompilerMojo and be done with it. This 
 way when we release 3.0-beta-1 the default source/target will be 1.5. I'll 
 also bump the locked down version of the maven-compiler-plugin I cut 
 accordingly.
 
 If I don't hear anything I'll assume that's fine and cut it.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder,  Apache Maven
 http://twitter.com/jvanzyl
 --
 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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

Re: Cutting another maven-compiler-plugin release to set the default source/target to 1.5

[Jason van Zyl]

On Apr 9, 2010, at 10:05 PM, Brett Porter wrote:

 This is the issue to update when you do:
 
 http://jira.codehaus.org/browse/MCOMPILER-80
 
 I agree it should be done, though for your purposes it might be more 
 expedient to put the configuration in the 3.0 super POM?
 

I think this would generally more useful in the plugin. I'm sure folks using 
2.x want this as well and we can cut a release of that soon to flip the default 
version in the POM. It's going to be 3 days anyway for beta-1 so it's not a big 
deal.

 - Brett
 
 On 10/04/2010, at 10:58 AM, Jason van Zyl wrote:
 
 The defaults are currently set in the plexus-compiler-javac component (to 
 source=1.3 and target=1.1) and not in the maven-compiler-plugin. I would 
 just like to set the default in the AbstractCompilerMojo and be done with 
 it. This way when we release 3.0-beta-1 the default source/target will be 
 1.5. I'll also bump the locked down version of the maven-compiler-plugin I 
 cut accordingly.
 
 If I don't hear anything I'll assume that's fine and cut it.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder,  Apache Maven
 http://twitter.com/jvanzyl
 --
 
 
 --
 Brett Porter
 br...@apache.org
 http://brettporter.wordpress.com/
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 

Thanks,

Jason

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