+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 ma
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
---
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
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.apa
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 Hein
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 Hein
Yes, I (or someone else, hint hint;) will look through all the issues
with patches.
Kristian
Den 26. aug. 2011 kl. 18:36 skrev Jesse Glick :
> On 08/26/2011 01:51 AM, Kristian Rosenvold wrote:
>> aiming for a release sometime mid-next week
>
> Please consider including the fix for MCOMPILER-140
On 08/26/2011 01:51 AM, Kristian Rosenvold wrote:
aiming for a release sometime mid-next week
Please consider including the fix for MCOMPILER-140 if you cut a release. It
has been sitting there with a patch for months with no activity.
I figured I'd try to fix the java7 compiler plugin issue over the
weekend, aiming for a release sometime mid-next week. Anyone wishing to
join in a little bug-scrub on the compiler plugin ?
Kristian
-
To unsubscribe, e-mail:
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 us
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 plug
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 woul
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 curre
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
14 matches
Mail list logo
