Cool !
+1
2010/4/11 Jason van Zyl
> On Apr 11, 2010, at 2:02 AM, nicolas de loof wrote:
>
> > Will this change be supported in m2eclipse ? I mean : will m2e detect the
> > maven-compiler-plugin 2.3+ version and set JRE1.5 classpath container ?
> >
>
> Configurators operate on the effective POM.
On Apr 11, 2010, at 2:02 AM, nicolas de loof wrote:
> Will this change be supported in m2eclipse ? I mean : will m2e detect the
> maven-compiler-plugin 2.3+ version and set JRE1.5 classpath container ?
>
Configurators operate on the effective POM. So when we update M2Eclipse to use
3.0-beta-1 w
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
+1
-Lukas
Jason van Zyl wrote:
Hi,
This was simply to bump the default source/target to 1.5. I don't want
3.0-beta-1 released requiring people to set these as they should be defaults
now.
Staging repo:
https://repository.apache.org/content/repositories/maven-011
All we fixed was this:
ht
