Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Olivier Lamy
So as no objections it's now merged. I bumped plexus-compiler version to 2.0-SNAPSHOT. As maven-compiler-plugin has a lot of changes (including incremental stuff) I wonder about bump version to 3.0-SNAPSHOT ? 2012/10/18 Olivier Lamy ol...@apache.org: just FYI I have created a branch here

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Arnaud Héritier
+1 to bump the compiler to 3.0 with this change On Fri, Oct 19, 2012 at 12:30 PM, Olivier Lamy ol...@apache.org wrote: So as no objections it's now merged. I bumped plexus-compiler version to 2.0-SNAPSHOT. As maven-compiler-plugin has a lot of changes (including incremental stuff) I wonder

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Anders Hammar
Just a question regarding plexus-compiler: Is it known to be used by anything but the m-compiler-p? As we're bumping to v2.0, how about breaking backwards compatibility? I'm thinking that we should change the signature of Compiler.compile so that it doesn't just return a list of messages, but

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Benson Margulies
On Fri, Oct 19, 2012 at 7:16 AM, Anders Hammar and...@hammar.net wrote: Just a question regarding plexus-compiler: Is it known to be used by anything but the m-compiler-p? As we're bumping to v2.0, how about breaking backwards compatibility? I'm thinking that we should change the signature of

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Anders Hammar
Changing the version number to 2.0 is not good enough to make incompatible changes, due to the working of dependency resolution. Sure it is, out of a configuration management perspective. Out of a Maven dep resolution perspective it might not be optimal. Preserving backwards compatibility is

Re: PLXCOMP-1 and improving compiler-message parsing

2012-10-19 Thread Olivier Lamy
I think this change makes sense. But I know at least one external dependency: http://groovy.codehaus.org/Groovy-Eclipse+compiler+plugin+for+Maven I don't know if Andrew is listening here ? 2012/10/19 Anders Hammar and...@hammar.net: Changing the version number to 2.0 is not good enough to make

git-workspace-plugin

2012-10-19 Thread Mark Derricutt
Hi all, Did any thing come of the [1] git-workspace-plugin discussed a few weeks ago? Were there any code spikes done in the end? Mark [1] https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin - To

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #27

2012-10-19 Thread Dennis Lundberg
See below... On 2012-10-19 18:50, Apache Jenkins Server wrote: See https://builds.apache.org/job/maven-plugins-ITs-m3-windows/27/changes Changes: [Robert Scholte] Add @since [Robert Scholte] Small code-optimizations -- [...truncated 9843

Re: git-workspace-plugin

2012-10-19 Thread Kristian Rosenvold
I did some initial doodles, but then I got caught up in maven-shared-utils. And so the days pass ;) I still haven't made up my mind if I should release maven 3.0.5 or work on the workspace-plugin once we do a release of m-s-u. But it's definitely going to be one of them ;) Kristian 2012/10/19

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #27

2012-10-19 Thread Robert Scholte
Dennis, I noticed exactly the same thing and since I'm in the same timezone there's not much I can do. The issue with the m-scm-publish-p is probably caused by SCM-435 I've fix it locally but I'm having trouble to push it back upstream, now that it is put in GIT. I haven't had a look at the