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
