Re: [VOTE] Release Maven WAR Plugin version 2.3

On Fri, 28 Sep 2012 21:38:00 +0100 (BST) Mark Struberg wrote: +1 (none-binding) thanks! tony, > +1 > > LieGrue, > strub > > > > > - Original Message - > > From: Kristian Rosenvold > > To: Maven Developers List > > Cc: > > Sent: Friday, September 28, 2012 10:11 PM > > Subject: R

Re: Reverted commit in changelog-plugin

no problem, svn can revert such things easily too (even if I had to look at the doc since I don't do such things everyday) I should have tested before commit and found this stupid typo I did thanks Hervé Le vendredi 28 septembre 2012 21:15:54 Kristian Rosenvold a écrit : > Hervé; > > In an ef

Re: Build failed in Jenkins: maven-plugins-ITs-m2 #790

thanks Denis for the analysis I think the culprit is http://jira.codehaus.org/browse/MPLUGIN-227 and javadoc plugin is just intolerant at this case where there is some code in "unnamed" package: not a regression, just a case that wasn't seen in real world before the bug in plugin tools I just

Re: Build failed in Jenkins: maven-plugins-ITs-m2 #790

I captured the three command-arg files from 2.8 and 2.9, and compared them. Here's the only difference. It looks to me as if this is a difference at Oracle, and that the utils need to change to tolerate that blank line. 20c20 < 'http://download.oracle.com/javase/1.5.0/docs/api' '/Users/benson/asf/

Programmatically query maven repository (obscure question)

I put my question on stackoverflow, but then found this forum. http://stackoverflow.com/questions/12648444/maven-plugin-programmatically-query-maven-repository Anyone know where I can get info to

Re: Build failed in Jenkins: maven-plugins-ITs-m2 #790

On Fri, Sep 28, 2012 at 6:06 PM, Dennis Lundberg wrote: > Hi > > I had a look at why the Javadoc Plugin has started failing. At first it > seemed weird since there had been no code changes, but then it hit me > that a new version of said plugin had just been released, and therefor a > new site had

Re: Build failed in Jenkins: maven-plugins-ITs-m2 #790

Hi I had a look at why the Javadoc Plugin has started failing. At first it seemed weird since there had been no code changes, but then it hit me that a new version of said plugin had just been released, and therefor a new site had been published. After some digging I found out the reason for the f

Re: [VOTE] Release Maven WAR Plugin version 2.3

+1 LieGrue, strub - Original Message - > From: Kristian Rosenvold > To: Maven Developers List > Cc: > Sent: Friday, September 28, 2012 10:11 PM > Subject: Re: [VOTE] Release Maven WAR Plugin version 2.3 > > +1 > > > 2012/9/28 Olivier Lamy : >> +1 >> >> 2012/9/28 Dennis Lundber

Re: [VOTE] Release Maven WAR Plugin version 2.3

+1 2012/9/28 Olivier Lamy : > +1 > > 2012/9/28 Dennis Lundberg : >> Hi, >> >> We solved 7 issues: >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&styleName=Html&version=18298 >> >> There are still a couple of issues left in JIRA: >> http://jira.codehaus.org/secure/IssueNavigat

Re: How to find out if a dependency is a Maven plugin?

the documentation is here http://maven.apache.org/plugin-tools/maven-plugin- plugin/examples/using-annotations.html and a lot of plugins now use these annotations: http://jira.codehaus.org/browse/MPLUGIN-203 Regards, Hervé Le vendredi 28 septembre 2012 11:43:30 Sascha Vogt a écrit : > Am 28.09

Re: PLXCOMP-1 and improving compiler-message parsing

On 9/28/12 12:08 PM, Mark Struberg wrote: +1 Imo this comes hand 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 We might create a documentation page about "Strategies for targeting older Java versions" which outlines the animal-sniffer, etc Li

Re: PLXCOMP-1 and improving compiler-message parsing

+1 Imo this comes hand 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 We might create a documentation page about "Strategies for targeting older Java versions" which outlines the animal-sniffer, etc LieGrue, strub - Original Message

PLXCOMP-1 and improving compiler-message parsing

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

Re: [VOTE] Release Maven WAR Plugin version 2.3

+1 2012/9/28 Dennis Lundberg : > Hi, > > We solved 7 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&styleName=Html&version=18298 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11150&status=1 > >

Re: How to find out if a dependency is a Maven plugin?

:-) hey, no stress. I'd rather find out sooner rather than later. What I had wanted to do was to make use of some code (not via a mojo; just treat it as a normal jar dependency; just like we would any other jar dep) that is contained in another plugin (both controlled by me). So do I have to re

Re: How to find out if a dependency is a Maven plugin?

Am 28.09.2012 10:41, schrieb Jörg Schaible: > You're aware that modern Maven plugins use now real annotations themselves? I've heard of it, but the last time I searched for it (a few months ago) did not yet find any documentation or even core plugins using that mechanism to see how it looks like or

Re: How to find out if a dependency is a Maven plugin?

Hi Sascha, Sascha Vogt wrote: > Hi, > > Am 27.09.2012 18:42, schrieb Jörg Schaible: >> In M3 the plugins are no longer shared within the reactor i.e. each >> plugin is using its own classloader and can therefore have any arbitrary >> dependency. So if your plugin depends on another plugin, there

Re: How to find out if a dependency is a Maven plugin?

Hi, Am 27.09.2012 18:42, schrieb Jörg Schaible: > In M3 the plugins are no longer shared within the reactor i.e. each plugin > is using its own classloader and can therefore have any arbitrary > dependency. So if your plugin depends on another plugin, there should be no > difference to any othe

Re: How to find out if a dependency is a Maven plugin?

Hey Chris, I'm sorry :( This was not my intention. See the other mail, we found a workaround ;) Greetings -Sascha- Am 28.09.2012 07:50, schrieb Chris Graham: > Yes, thanks. You've send me back to the drawing board... > > On 28/09/2012, at 12:23 AM, Sascha Vogt wrote: > >> First of all, thank