Re: PLXCOMP-1 and improving compiler-message parsing

2012-11-09 Thread Anders Hammar
;>>>> > In compiler plugin (not committed yet), I have added a flag to > >> disable > >> >>>>>>> > use of javax.tools usage (as it if that breaks on some os/jdk > >> users > >> >>>>>>> > will be able to disable

Re: PLXCOMP-1 and improving compiler-message parsing

2012-11-08 Thread Olivier Lamy
even if that's detected to be usable) >> >>>>>>> > >> >>>>>>> > WDYT ? >> >>>>>>> > >> >>>>>>> > 2012/10/1 Stephen Connolly : >> >>>>>>> >> On

Re: PLXCOMP-1 and improving compiler-message parsing

2012-11-08 Thread Anders Hammar
>> >> On 28 September 2012 18:15, John Casey > wrote: > >>>>>>> >> > >>>>>>> >>> On 9/28/12 12:08 PM, Mark Struberg wrote: > >>>>>>> >>> > >>>>>>> >>>>

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-29 Thread Anders Hammar
and in hand with moving maven-core to 1.6 as well >>>>>>> >>>> and >>>>>>> a >>>>>>> >>>> version bump to mvn-3.2.0 or even mvn-3.5.0 >>>>>>> >>>> >>>>>>> >

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-28 Thread Olivier Lamy
documentation page about "Strategies for targeting >>>>>> >>>> older Java versions" which outlines the animal-sniffer, etc >>>>>> >>>> >>>>>> >>>> LieGrue, >>>>>> >>&g

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Olivier Lamy
rategies for targeting >>>>> >>>> older Java versions" which outlines the animal-sniffer, etc >>>>> >>>> >>>>> >>>> LieGrue, >>>>> >>>> strub >>>>> >>>> >>>>> >>> >>>>> >>> I thin

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Anders Hammar
; itself, >>>> >>> since people can still use the core + the older version of the compiler >>>> >>> plugin to run on 1.5... >>>> >>> >>>> >>> I wouldn't want to get mired in a discussion about when we're going to &g

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Benson Margulies
gt; I wouldn't want to get mired in a discussion about when we're going to >>> >>> move the core up to 1.6, since that's a bit more work. >>> >>> >>> >>> >>> >> There is the Toolchains issue. >>> >> >

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Anders Hammar
to get mired in a discussion about when we're going to >> >>> move the core up to 1.6, since that's a bit more work. >> >>> >> >>> >> >> There is the Toolchains issue. >> >> >> >> At present, AFAIK we can use Toolchains to run Maven with Java 1.6 and >> >> comp

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Arnaud Héritier
AFAIK we can use Toolchains to run Maven with Java 1.6 and > >> compile with Java 1.3. > >> > >> Surefire supports running tests via toolchains down to Java 1.3 IIRC > >> > >> If we are doing something that makes this kind of thing impossible *even > >&g

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Olivier Lamy
t;> >> Surefire supports running tests via toolchains down to Java 1.3 IIRC >> >> If we are doing something that makes this kind of thing impossible *even >> via toolchains* then my feeling is that I am -1. >> >> If we can find a way (more indirection please, it solves all problems don&#

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-18 Thread Olivier Lamy
m -1. > > If we can find a way (more indirection please, it solves all problems don't > you know) to allow this to work *and* retain toolchains support for > compiling with JDK 1.3 then +1. > > >> >> >>> >>> >>> >>> - Original Me

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-01 Thread Stephen Connolly
solves all problems don't you know) to allow this to work *and* retain toolchains support for compiling with JDK 1.3 then +1. > > >> >> >> >> ----- Original Message ----- >> >>> From: John Casey >>> To: Maven Developers List >>>

Re: PLXCOMP-1 and improving compiler-message parsing

2012-09-29 Thread Mark Struberg
+1 I see no reason to fumble with that stuff on foreign realms. LieGrue, strub - Original Message - > From: Olivier Lamy > To: Maven Developers List > Cc: > Sent: Saturday, September 29, 2012 3:53 PM > Subject: Re: PLXCOMP-1 and improving compiler-message parsin

Re: PLXCOMP-1 and improving compiler-message parsing

2012-09-29 Thread Olivier Lamy
.5... >>> >>> I wouldn't want to get mired in a discussion about when we're going to move >>> the core up to 1.6, since that's a bit more work. >>> >>> >>>> >>>> >>>> >>>> >>>&g

Re: PLXCOMP-1 and improving compiler-message parsing

2012-09-29 Thread Olivier Lamy
ore + the older version of the compiler >> plugin to run on 1.5... >> >> I wouldn't want to get mired in a discussion about when we're going to move >> the core up to 1.6, since that's a bit more work. >> >> >>> >>> >>> >>> >>> --

Re: PLXCOMP-1 and improving compiler-message parsing

2012-09-29 Thread Kristian Rosenvold
use the core + the older version of the compiler > plugin to run on 1.5... > > I wouldn't want to get mired in a discussion about when we're going to move > the core up to 1.6, since that's a bit more work. > > >> >> >> >> >> -

Re: PLXCOMP-1 and improving compiler-message parsing

2012-09-28 Thread John Casey
1.6, since that's a bit more work. - Original Message - From: John Casey To: Maven Developers List Cc: Sent: Friday, September 28, 2012 6:53 PM Subject: PLXCOMP-1 and improving compiler-message parsing Hi everyone, There's a new patch to the plexus-compiler libraries

Re: PLXCOMP-1 and improving compiler-message parsing

2012-09-28 Thread Mark Struberg
al Message - > From: John Casey > To: Maven Developers List > Cc: > Sent: Friday, September 28, 2012 6:53 PM > Subject: PLXCOMP-1 and improving compiler-message parsing > > Hi everyone, > > There's a new patch to the plexus-compiler libraries which impr

PLXCOMP-1 and improving compiler-message parsing

2012-09-28 Thread John Casey
Hi everyone, There's a new patch to the plexus-compiler libraries which improves the parsing of the output messages, especially for annotation processing. Previously, a lot of non-error messages caused plexus-compiler (and thereby, Maven) to think a compilation error had occurred. The patch f