Re: [VOTE] Release Apache Maven 3.0
+1 Niall On Mon, Oct 4, 2010 at 1:16 PM, Benjamin Bentmann wrote: > Hi, > > feedback on the RCs seems to be decreasing and I am currently not aware of > any major regression so let's try and cross the finishing line of this > marathon. > > We solved 31 issues since 3.0-beta-3: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-004/ > > Staged source and binary distros: > https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > +1 from me > > > Benjamin > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Julia Antonova/Tumlare is out of office.
27 days so far this year! - but I'm not surprised since she works for a holiday company: http://tumlare.com/ Niall On Sun, Jun 27, 2010 at 11:19 PM, Julia Antonova wrote: > > I will be out of the office starting 28.06.2010 and will not return until > 29.06.2010. > > I have no acces to my mailbox, I will reply to your message upon return. > For urgent issues please contact my colleagues: > Sergey Khomyakov / Administration - serge...@tumlare.com > Irina Pashina / Administration - secretary...@tumlare.com > Thank you! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-beta-1
On Tue, Apr 20, 2010 at 8:48 AM, Olivier Lamy wrote:
> No.
> It's 3.x prerequisite.
It would be good if there was some mechanism so that the site
generation could be made to work with either m2 or m3. Perhaps by
activating different profiles dependant on the maven version -
something like:
org.apache.maven.plugins
maven-site-plugin
${site.plugin.version}
2
2.0.1
3
3.0-beta-1
> 2010/4/20 Brett Porter :
>>
>> On 20/04/2010, at 5:10 PM, Olivier Lamy wrote:
>>
>>> Hi,
>>>
>>> 2010/4/20 Hervé BOUTEMY :
what about releasing maven-site-plugin 3.0-beta-1?
>>>
>>> Yup I can do that and start releasing all needed stuff.
>>>
Olivier, is there something critical missing?
>>>
>>> No except some spare time :-)
>>
>> Does that also work with Maven 2.x, or will we end up having two strands of
>> development on it?
>>
>> - Brett
>>
>> --
>> Brett Porter
>> br...@apache.org
>> http://brettporter.wordpress.com/
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
>
> --
> Olivier
> http://twitter.com/olamy
> http://fr.linkedin.com/in/olamy
> http://www.viadeo.com/fr/profile/olivier.lamy7
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
m3 report generation
Is there any info on how to get report generation to work using m3? (when I generate a site using 3.0-alpha-7 none of the reports get generated - either then *standard* reports from maven-project-info-reports-plugin or anything defined in the section) Thanks Niall - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [jira] Closed: (SUREFIRE-591) Add maven-failsafe-plugin to surefire project
On Sat, Jan 9, 2010 at 2:27 PM, Dennis Lundberg wrote: > Do we have a problem with the mailing lists? > > I didn't receive a mail about this commit. I have a gap between commits > r896444 and r897254 in my mail. It's ~51 hours. The mail archives > indicate the same thing. > > I can see the commit here though: > http://svn.apache.org/viewvc?view=revision&revision=897127 Looks like it went to the surefire-commits list rather than the maven commits list: http://mail-archives.apache.org/mod_mbox/maven-surefire-commits/201001.mbox/browser Niall > Stephen Connolly (JIRA) wrote: >> [ >> http://jira.codehaus.org/browse/SUREFIRE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> Stephen Connolly closed SUREFIRE-591. >> - >> >> Resolution: Fixed >> Fix Version/s: 2.5 >> >> r897127. >> >>> Add maven-failsafe-plugin to surefire project >>> - >>> >>> Key: SUREFIRE-591 >>> URL: http://jira.codehaus.org/browse/SUREFIRE-591 >>> Project: Maven Surefire >>> Issue Type: New Feature >>> Components: plugin >>> Reporter: Stephen Connolly >>> Assignee: Stephen Connolly >>> Fix For: 2.5 >>> >>> >>> The failsafe-maven-plugin is a fork of maven-surefire-plugin which is used >>> when running integration tests. In order to simplify maintenance, rehost >>> this plugin @apache rather than @codehaus >> > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-alpha-5
On Mon, Nov 23, 2009 at 7:59 PM, Paul Gier wrote: > I wonder if we really need a full vote for every alpha. Especially if this > is going to happen every two weeks. Why not just vote for a 2 week alpha > release schedule and then don't do another vote until it's time for beta 1? The ASF requires a vote on the artifacts being released. You can't just sign a blank cheque for any future release. On that basis someone could put something that isn't allowed (e.g. a copy of some GPL code) into maven and then just cut an alpha release. I tried to find something in the ASF docs, but the release FAQ only says "Each PMC must obey the ASF requirements on approving any release" - but I can't find something that specifically says what the "requirements on approving any release" are. http://www.apache.org/dev/release.html Niall > Benjamin Bentmann wrote: >> >> Hi, >> >> We solved some more issues: >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14952 >> >> There are still a couple of issues left in JIRA: >> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-018/ >> >> Staged source and binary distros: >> >> https://repository.apache.org/content/repositories/maven-018/org/apache/maven/apache-maven/3.0-alpha-5/ >> >> Guide to testing staged releases: >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> +1 from me >> >> >> Benjamim >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: preparing for the next 3.x alpha release
On Thu, Oct 22, 2009 at 8:04 PM, Brian Fox wrote: > Just summing up a conversation I had with Jason and Benjamin: After > Benjamin finishes up the current issue MNG-4221 > (http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=14719&resolution=-1&sorter/field=issuekey&sorter/order=DESC) > then we think it's time to prepare the next Alpha release. This > release won't support reporting plugins and thus sites with reports, > but otherwise it appears to be pretty stable. Another alpha release would be good. Besides fixing compatibility issues, is the main TODO completing the reporting refactoring[1] before its ready for beta, or are there other things as well? Niall [1] http://jira.codehaus.org/browse/MNG-4162 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Problems running with commons ant plugin with maven3
On Fri, Oct 16, 2009 at 10:13 PM, Olivier Lamy wrote: > Hi, > Plexus 1.4.0-SNAPSHOT is here : > https://svn.codehaus.org/plexus/plexus-containers/branches/plexus-containers-1.x/. Thanks Olivier that sorted out my maven-3 build problem - but I still get a failure in my ant plugin. I created an bug report here: http://jira.codehaus.org/browse/MNG-4396 Hopefully thats in the correct place Niall > Or you can add this repository [1] in your settings > > -- > Olivier > > [1] http://repository.sonatype.org/content/groups/forge/ > > 2009/10/16 Niall Pemberton : >> I checked out and built maven3 (after reverting the plexus version >> from 1.4.0-SNAPSHOT to 1.3.0) and tried to run the >> commons-build-plugin[1] (which is an Ant plugin) and it failed (some >> of the output with -X shown below) >> >> So I thought this might be caused by me reverting the plexus version. >> So I checked out plexus from http://svn.codehaus.org/plexus/trunks but >> found that the version in its pom is 1.2-SNAPSHOT. So where can I find >> plexus 1.4.0-SNAPSHOT? >> >> Niall >> >> [1] http://commons.apache.org/commons-build-plugin/ >> >> >> [ERROR] : Unable to find the mojo 'jira-page' (or one of its required >> components) in the plugin >> 'org.apache.commons:commons-build-plugin:1.1' >> >> Caused by: >> org.codehaus.plexus.component.repository.exception.ComponentLookupException: >> Unable to lookup component 'org.apache.maven.plugin.Mojo', it could >> not be started. >> role: org.apache.maven.plugin.Mojo >> roleHint: org.apache.commons:commons-build-plugin:1.1:jira-page >> classRealm: plugin>org.apache.commons:commons-build-plugin:1.1 >> at >> org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:366) >> at >> org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) >> at >> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:388) >> at >> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:488) >> ... 15 more >> Caused by: >> org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: >> Error constructing component role: 'org.apache.maven.plugin.Mojo', >> implementation: '/generate-xdocs.build.xml:jira-page', role hint: >> 'org.apache.commons:commons-build-plugin:1.1:jira-page' >> at >> org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:178) >> at >> org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) >> at >> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) >> at >> org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:51) >> at >> org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:351) >> ... 18 more >> Caused by: java.lang.AbstractMethodError: >> org.apache.maven.script.ant.AntMojoComponentFactory.newInstance(Lorg/codehaus/plexus/component/repository/ComponentDescriptor;Lorg/codehaus/plexus/classworlds/realm/ClassRealm;Lorg/codehaus/plexus/PlexusContainer;)Ljava/lang/Object; >> at >> org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:163) >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > > > -- > Olivier > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Problems running with commons ant plugin with maven3
I checked out and built maven3 (after reverting the plexus version from 1.4.0-SNAPSHOT to 1.3.0) and tried to run the commons-build-plugin[1] (which is an Ant plugin) and it failed (some of the output with -X shown below) So I thought this might be caused by me reverting the plexus version. So I checked out plexus from http://svn.codehaus.org/plexus/trunks but found that the version in its pom is 1.2-SNAPSHOT. So where can I find plexus 1.4.0-SNAPSHOT? Niall [1] http://commons.apache.org/commons-build-plugin/ [ERROR] : Unable to find the mojo 'jira-page' (or one of its required components) in the plugin 'org.apache.commons:commons-build-plugin:1.1' Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojo', it could not be started. role: org.apache.maven.plugin.Mojo roleHint: org.apache.commons:commons-build-plugin:1.1:jira-page classRealm: plugin>org.apache.commons:commons-build-plugin:1.1 at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:366) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:388) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:488) ... 15 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.plugin.Mojo', implementation: '/generate-xdocs.build.xml:jira-page', role hint: 'org.apache.commons:commons-build-plugin:1.1:jira-page' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:178) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:51) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:351) ... 18 more Caused by: java.lang.AbstractMethodError: org.apache.maven.script.ant.AntMojoComponentFactory.newInstance(Lorg/codehaus/plexus/component/repository/ComponentDescriptor;Lorg/codehaus/plexus/classworlds/realm/ClassRealm;Lorg/codehaus/plexus/PlexusContainer;)Ljava/lang/Object; at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:163) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Building m2 guide needs to be updated for new maven-3 location
Also, I hit a couple of snags when I tried to build - perhaps the guide could be updated to mention these 1) the plexus version has been updated to 1.4.0-SNAPSHOT[3] which prevents maven-3 module from building. I changed the version back to 1.3.0 locally to get the build to work 2) The build fails if subversion is not installed Niall [3] https://svn.apache.org/viewvc?view=revision&revision=823551 On Fri, Oct 16, 2009 at 4:22 PM, Niall Pemberton wrote: > The building m2 guide is out of date for maven-3[1] since it moved[2] > location in the repository > > Niall > > [1] http://maven.apache.org/guides/development/guide-building-m2.html > [2] https://svn.apache.org/viewvc?view=revision&revision=811356 > > > > > > Index: site/apt/guides/development/guide-building-m2.apt > === > --- site/apt/guides/development/guide-building-m2.apt (revision 825923) > +++ site/apt/guides/development/guide-building-m2.apt (working copy) > @@ -52,11 +52,11 @@ > svn co https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x > maven-2.2.x > --- > > - To build Maven 3.0 (unstable development branch), you need the > <<>> of the <<>> module. To > + To build Maven 3.0 (unstable development branch), you need the > <<>> of the <<>> module. To > check that out, run the command: > > --- > -svn co https://svn.apache.org/repos/asf/maven/components/trunk maven-3 > +svn co https://svn.apache.org/repos/asf/maven/maven-3/trunk/ maven-3 > --- > > Alternatively, you can check out all Maven projects in one directory using: > @@ -66,7 +66,7 @@ > --- > > If you have checked out <<>>, the <<>> directory will > - contain the Maven 2.2 source code, and the <<>> directory will > + contain the Maven 2.2 source code, and the <<>> directory will > contain the 3.0 source code. Note that neither directory contains any of the > plugins. > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Building m2 guide needs to be updated for new maven-3 location
The building m2 guide is out of date for maven-3[1] since it moved[2] location in the repository Niall [1] http://maven.apache.org/guides/development/guide-building-m2.html [2] https://svn.apache.org/viewvc?view=revision&revision=811356 Index: site/apt/guides/development/guide-building-m2.apt === --- site/apt/guides/development/guide-building-m2.apt (revision 825923) +++ site/apt/guides/development/guide-building-m2.apt (working copy) @@ -52,11 +52,11 @@ svn co https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x maven-2.2.x --- - To build Maven 3.0 (unstable development branch), you need the <<>> of the <<>> module. To + To build Maven 3.0 (unstable development branch), you need the <<>> of the <<>> module. To check that out, run the command: --- -svn co https://svn.apache.org/repos/asf/maven/components/trunk maven-3 +svn co https://svn.apache.org/repos/asf/maven/maven-3/trunk/ maven-3 --- Alternatively, you can check out all Maven projects in one directory using: @@ -66,7 +66,7 @@ --- If you have checked out <<>>, the <<>> directory will - contain the Maven 2.2 source code, and the <<>> directory will + contain the Maven 2.2 source code, and the <<>> directory will contain the 3.0 source code. Note that neither directory contains any of the plugins. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
On Sat, Mar 28, 2009 at 10:53 PM, Brian E. Fox wrote: > All set. Thanks Niall > -Original Message- > From: Niall Pemberton [mailto:niall.pember...@gmail.com] > Sent: Saturday, March 28, 2009 5:52 PM > To: Maven Developers List > Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released > > The parent pom doesn't seem to have found its way to the public repo > yet, is it on its way? > > http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/ > > Niall > > On Sat, Mar 28, 2009 at 5:36 PM, Olivier Lamy wrote: >> Hi, >> The Maven team is pleased to announce the release of the Maven Release >> Plugin, version 2.0-beta-9. >> >> http://maven.apache.org/plugins/maven-release-plugin/ >> >> You should specify the version in your project's plugin configuration: >> >> >> org.apache.maven.plugins >> maven-release-plugin >> 2.0-beta-9 >> >> >> >> Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9 >> >> >> ** Bug >> * [MRELEASE-273] - Regression: NullPointerException at end of >> standalone "release:perform" >> * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0 >> * [MRELEASE-379] - return results after performing a release >> * [MRELEASE-381] - url syntax not good enough for the git scm provider >> * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform() >> * [MRELEASE-393] - NoSuchMethodError when using >> InvokerMavenExecutor with cmd line arg "--quiet" >> * [MRELEASE-405] - Wrong branch-name parameter >> >> ** Improvement >> * [MRELEASE-385] - Upgrade to last scm version (1.2) >> * [MRELEASE-392] - Align release-parent, release-manager and >> release-plugin versions >> * [MRELEASE-427] - Add a mojo parameter for using the new remote >> tagging for svn scm provider (to prevent issue with svn > 1.5.0) >> * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to >> [number]-SNAPSHOT >> >> >> ** Task >> * [MRELEASE-390] - Add VSS dependency >> >> Have Fun! >> >> -- >> The Maven Team >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
The parent pom doesn't seem to have found its way to the public repo yet, is it on its way? http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/ Niall On Sat, Mar 28, 2009 at 5:36 PM, Olivier Lamy wrote: > Hi, > The Maven team is pleased to announce the release of the Maven Release > Plugin, version 2.0-beta-9. > > http://maven.apache.org/plugins/maven-release-plugin/ > > You should specify the version in your project's plugin configuration: > > > org.apache.maven.plugins > maven-release-plugin > 2.0-beta-9 > > > > Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9 > > > ** Bug > * [MRELEASE-273] - Regression: NullPointerException at end of > standalone "release:perform" > * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0 > * [MRELEASE-379] - return results after performing a release > * [MRELEASE-381] - url syntax not good enough for the git scm provider > * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform() > * [MRELEASE-393] - NoSuchMethodError when using > InvokerMavenExecutor with cmd line arg "--quiet" > * [MRELEASE-405] - Wrong branch-name parameter > > ** Improvement > * [MRELEASE-385] - Upgrade to last scm version (1.2) > * [MRELEASE-392] - Align release-parent, release-manager and > release-plugin versions > * [MRELEASE-427] - Add a mojo parameter for using the new remote > tagging for svn scm provider (to prevent issue with svn > 1.5.0) > * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to > [number]-SNAPSHOT > > > ** Task > * [MRELEASE-390] - Add VSS dependency > > Have Fun! > > -- > The Maven Team > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Problem finding loadresource task in maven 2.0.9
On Mon, Jun 30, 2008 at 3:10 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Can you file a jira and attach a project that reproduces the issue? This > will be the best way for us to figure out what's up. There were some > changes between 2.0.8-9 that may cause this (and wouldn't be bugs per > se), but we won't know until we look. If it truly is a regression, we > want to fix it for .10. OK I've filed the following issue, with a simple pom.xml attached: http://jira.codehaus.org/browse/MNG-3639 Niall > -Original Message- > From: Niall Pemberton [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 29, 2008 11:08 AM > To: Maven Developers List > Subject: Re: Problem finding loadresource task in maven 2.0.9 > > On Sun, Jun 29, 2008 at 3:42 PM, Dennis Lundberg <[EMAIL PROTECTED]> > wrote: >> Niall Pemberton wrote: >>> >>> On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers > <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> What does -X tell you? >>> >>> Not alot that makes any sense to me, but thanks for the suggestion - > I >>> ran it with that option for both maven 2.0.8 and 2.0.9 and the output >>> for both is here: >>> >>> http://people.apache.org/~niallp/commons-build-plugin/ >> >> The stack trace helped me find where I had seen this before. It is a > bug in >> Ant 1.7.0, that has been fixed in Ant 1.7.1 on 2007-05-22. It is not >> properly handling spaces in paths. Unfortunately there has not yet > been a >> release of Ant 1.7.1. > > Sorry I'm a bit confused - seems like you're referring to the issue I > had described in the following thread when I upgraded from maven 2.0.7 > to 2.0.8, rather than this issue with not finding the loadresource > task when I upgraded from 2.0.8 to 2.0.9: > > http://markmail.org/message/hmwabpxrq76mbp3l > > ...or is this somehow related? > > Niall > >>> >>> Niall >>> >>>> Niall Pemberton wrote: >>>>> >>>>> Anyone got any ideas on this - should I open a JIRA ticket (if so >>>>> against what?) or should I have asked this on the user list? I > posted >>>>> here coz it looks like a maven bug to me. >>>>> >>>>> Niall >>>>> >>>>> On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton >>>>> <[EMAIL PROTECTED]> wrote: >>>>> >>>>>> I recently upgraded from maven 2.0.8 to 2.0.9 and the >>>>>> commons-build-plugin[1][2] - which is an Ant plugin - failed with > the >>>>>> following error >>>>>> >>>>>> INFO] >>>>>> >>>>>> > >>>>>> [INFO] Building Commons JNet >>>>>> [INFO]task-segment: [commons:sandbox-jira-page] >>>>>> [INFO] >>>>>> >>>>>> > >>>>>> [INFO] [commons:sandbox-jira-page] >>>>>> >>>>>> sandbox-jira-page: >>>>>> [echo] *** Generating Commons JNet Sandbox Issue Tracking Page > *** >>>>>> [mkdir] Created dir: >>>>>> C:\svn\commons\trunks-sandbox\jnet\target\commons-generated-xdocs >>>>>> [INFO] >>>>>> >>>>>> > >>>>>> [ERROR] BUILD ERROR >>>>>> [INFO] >>>>>> >>>>>> > >>>>>> [INFO] Failed to execute: Executing Ant script: >>>>>> /generate-xdocs.build.xml [sandbox-jira-page]: Failed to execute. >>>>>> >>>>>> Could not create task or type of type: loadresource. >>>>>> >>>>>> The plugin specifies version 1.7.0 of Ant in its pom[3] > specifically >>>>>> because the loadresource task was introduce in that version. >>>>>> >>>>>> Reverting to maven 2.0.8 and the problem goes away. Any ideas? Is > this >>>>>> a known issue in 2.0.9? >>>>>> >>>>>> Niall >>>>>> >>>>>> [1] http://commons.apache.org/commons-build-plugin/ >>>>>> [2] >>>>>> > http://commons.apache.org/commons-build-plugin/source-repository.html >>>>>> [3] >>>>>> >>>>>> > http://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/trun > k/pom.xml > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem finding loadresource task in maven 2.0.9
On Sun, Jun 29, 2008 at 3:42 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Niall Pemberton wrote: >> >> On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]> >> wrote: >>> >>> What does -X tell you? >> >> Not alot that makes any sense to me, but thanks for the suggestion - I >> ran it with that option for both maven 2.0.8 and 2.0.9 and the output >> for both is here: >> >> http://people.apache.org/~niallp/commons-build-plugin/ > > The stack trace helped me find where I had seen this before. It is a bug in > Ant 1.7.0, that has been fixed in Ant 1.7.1 on 2007-05-22. It is not > properly handling spaces in paths. Unfortunately there has not yet been a > release of Ant 1.7.1. Sorry I'm a bit confused - seems like you're referring to the issue I had described in the following thread when I upgraded from maven 2.0.7 to 2.0.8, rather than this issue with not finding the loadresource task when I upgraded from 2.0.8 to 2.0.9: http://markmail.org/message/hmwabpxrq76mbp3l ...or is this somehow related? Niall >> >> Niall >> >>> Niall Pemberton wrote: >>>> >>>> Anyone got any ideas on this - should I open a JIRA ticket (if so >>>> against what?) or should I have asked this on the user list? I posted >>>> here coz it looks like a maven bug to me. >>>> >>>> Niall >>>> >>>> On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton >>>> <[EMAIL PROTECTED]> wrote: >>>> >>>>> I recently upgraded from maven 2.0.8 to 2.0.9 and the >>>>> commons-build-plugin[1][2] - which is an Ant plugin - failed with the >>>>> following error >>>>> >>>>> INFO] >>>>> >>>>> >>>>> [INFO] Building Commons JNet >>>>> [INFO]task-segment: [commons:sandbox-jira-page] >>>>> [INFO] >>>>> >>>>> >>>>> [INFO] [commons:sandbox-jira-page] >>>>> >>>>> sandbox-jira-page: >>>>> [echo] *** Generating Commons JNet Sandbox Issue Tracking Page *** >>>>> [mkdir] Created dir: >>>>> C:\svn\commons\trunks-sandbox\jnet\target\commons-generated-xdocs >>>>> [INFO] >>>>> >>>>> >>>>> [ERROR] BUILD ERROR >>>>> [INFO] >>>>> >>>>> >>>>> [INFO] Failed to execute: Executing Ant script: >>>>> /generate-xdocs.build.xml [sandbox-jira-page]: Failed to execute. >>>>> >>>>> Could not create task or type of type: loadresource. >>>>> >>>>> The plugin specifies version 1.7.0 of Ant in its pom[3] specifically >>>>> because the loadresource task was introduce in that version. >>>>> >>>>> Reverting to maven 2.0.8 and the problem goes away. Any ideas? Is this >>>>> a known issue in 2.0.9? >>>>> >>>>> Niall >>>>> >>>>> [1] http://commons.apache.org/commons-build-plugin/ >>>>> [2] >>>>> http://commons.apache.org/commons-build-plugin/source-repository.html >>>>> [3] >>>>> >>>>> http://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/trunk/pom.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem finding loadresource task in maven 2.0.9
On Sun, Jun 29, 2008 at 5:20 AM, Ralph Goers <[EMAIL PROTECTED]> wrote: > This caught my eye. I have no idea what it means though or if it could be > responsible for the problem. > > The following artifacts were filtered out for plugin: > org.apache.commons:commons-build-plugin:1.0 because they're already in the > core of Maven: Seems that is output by the DefaultPluginManager (see http://tinyurl.com/4jxr64 ) - but since nothing is listed after that statement, it doesn't look like anything has been filtered out. Sinec from the -X output for maven 2.0.9 it is clearly showing Ant 1.7.0 as a dependency then presumably this is some kind of bug in building the classpath for the plugin and it is picking up an earlier Ant version (and therefore not finding the 1.7.0 specific task) before Ant 1.7.0. Debugging the internals though is beyond my maven knowledge. Niall > Niall Pemberton wrote: >> >> On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]> >> wrote: >> >>> >>> What does -X tell you? >>> >> >> Not alot that makes any sense to me, but thanks for the suggestion - I >> ran it with that option for both maven 2.0.8 and 2.0.9 and the output >> for both is here: >> >> http://people.apache.org/~niallp/commons-build-plugin/ >> >> Niall >> >> >>> >>> Niall Pemberton wrote: >>> >>>> >>>> Anyone got any ideas on this - should I open a JIRA ticket (if so >>>> against what?) or should I have asked this on the user list? I posted >>>> here coz it looks like a maven bug to me. >>>> >>>> Niall >>>> >>>> On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton >>>> <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>> >>>>> I recently upgraded from maven 2.0.8 to 2.0.9 and the >>>>> commons-build-plugin[1][2] - which is an Ant plugin - failed with the >>>>> following error >>>>> >>>>> INFO] >>>>> >>>>> >>>>> [INFO] Building Commons JNet >>>>> [INFO]task-segment: [commons:sandbox-jira-page] >>>>> [INFO] >>>>> >>>>> >>>>> [INFO] [commons:sandbox-jira-page] >>>>> >>>>> sandbox-jira-page: >>>>> [echo] *** Generating Commons JNet Sandbox Issue Tracking Page *** >>>>> [mkdir] Created dir: >>>>> C:\svn\commons\trunks-sandbox\jnet\target\commons-generated-xdocs >>>>> [INFO] >>>>> >>>>> >>>>> [ERROR] BUILD ERROR >>>>> [INFO] >>>>> >>>>> >>>>> [INFO] Failed to execute: Executing Ant script: >>>>> /generate-xdocs.build.xml [sandbox-jira-page]: Failed to execute. >>>>> >>>>> Could not create task or type of type: loadresource. >>>>> >>>>> The plugin specifies version 1.7.0 of Ant in its pom[3] specifically >>>>> because the loadresource task was introduce in that version. >>>>> >>>>> Reverting to maven 2.0.8 and the problem goes away. Any ideas? Is this >>>>> a known issue in 2.0.9? >>>>> >>>>> Niall >>>>> >>>>> [1] http://commons.apache.org/commons-build-plugin/ >>>>> [2] >>>>> http://commons.apache.org/commons-build-plugin/source-repository.html >>>>> [3] >>>>> >>>>> http://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/trunk/pom.xml >>>>> >>>>> >>>>> >>>> >>>> - >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem finding loadresource task in maven 2.0.9
On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]> wrote: > What does -X tell you? Not alot that makes any sense to me, but thanks for the suggestion - I ran it with that option for both maven 2.0.8 and 2.0.9 and the output for both is here: http://people.apache.org/~niallp/commons-build-plugin/ Niall > Niall Pemberton wrote: >> >> Anyone got any ideas on this - should I open a JIRA ticket (if so >> against what?) or should I have asked this on the user list? I posted >> here coz it looks like a maven bug to me. >> >> Niall >> >> On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton >> <[EMAIL PROTECTED]> wrote: >> >>> >>> I recently upgraded from maven 2.0.8 to 2.0.9 and the >>> commons-build-plugin[1][2] - which is an Ant plugin - failed with the >>> following error >>> >>> INFO] >>> >>> [INFO] Building Commons JNet >>> [INFO]task-segment: [commons:sandbox-jira-page] >>> [INFO] >>> >>> [INFO] [commons:sandbox-jira-page] >>> >>> sandbox-jira-page: >>>[echo] *** Generating Commons JNet Sandbox Issue Tracking Page *** >>> [mkdir] Created dir: >>> C:\svn\commons\trunks-sandbox\jnet\target\commons-generated-xdocs >>> [INFO] >>> >>> [ERROR] BUILD ERROR >>> [INFO] >>> >>> [INFO] Failed to execute: Executing Ant script: >>> /generate-xdocs.build.xml [sandbox-jira-page]: Failed to execute. >>> >>> Could not create task or type of type: loadresource. >>> >>> The plugin specifies version 1.7.0 of Ant in its pom[3] specifically >>> because the loadresource task was introduce in that version. >>> >>> Reverting to maven 2.0.8 and the problem goes away. Any ideas? Is this >>> a known issue in 2.0.9? >>> >>> Niall >>> >>> [1] http://commons.apache.org/commons-build-plugin/ >>> [2] http://commons.apache.org/commons-build-plugin/source-repository.html >>> [3] >>> http://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/trunk/pom.xml >>> >>> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem finding loadresource task in maven 2.0.9
Anyone got any ideas on this - should I open a JIRA ticket (if so against what?) or should I have asked this on the user list? I posted here coz it looks like a maven bug to me. Niall On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote: > I recently upgraded from maven 2.0.8 to 2.0.9 and the > commons-build-plugin[1][2] - which is an Ant plugin - failed with the > following error > > INFO] > [INFO] Building Commons JNet > [INFO]task-segment: [commons:sandbox-jira-page] > [INFO] > > [INFO] [commons:sandbox-jira-page] > > sandbox-jira-page: > [echo] *** Generating Commons JNet Sandbox Issue Tracking Page *** >[mkdir] Created dir: > C:\svn\commons\trunks-sandbox\jnet\target\commons-generated-xdocs > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to execute: Executing Ant script: > /generate-xdocs.build.xml [sandbox-jira-page]: Failed to execute. > > Could not create task or type of type: loadresource. > > The plugin specifies version 1.7.0 of Ant in its pom[3] specifically > because the loadresource task was introduce in that version. > > Reverting to maven 2.0.8 and the problem goes away. Any ideas? Is this > a known issue in 2.0.9? > > Niall > > [1] http://commons.apache.org/commons-build-plugin/ > [2] http://commons.apache.org/commons-build-plugin/source-repository.html > [3] > http://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/trunk/pom.xml > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem finding loadresource task in maven 2.0.9
I recently upgraded from maven 2.0.8 to 2.0.9 and the commons-build-plugin[1][2] - which is an Ant plugin - failed with the following error INFO] [INFO] Building Commons JNet [INFO]task-segment: [commons:sandbox-jira-page] [INFO] [INFO] [commons:sandbox-jira-page] sandbox-jira-page: [echo] *** Generating Commons JNet Sandbox Issue Tracking Page *** [mkdir] Created dir: C:\svn\commons\trunks-sandbox\jnet\target\commons-generated-xdocs [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to execute: Executing Ant script: /generate-xdocs.build.xml [sandbox-jira-page]: Failed to execute. Could not create task or type of type: loadresource. The plugin specifies version 1.7.0 of Ant in its pom[3] specifically because the loadresource task was introduce in that version. Reverting to maven 2.0.8 and the problem goes away. Any ideas? Is this a known issue in 2.0.9? Niall [1] http://commons.apache.org/commons-build-plugin/ [2] http://commons.apache.org/commons-build-plugin/source-repository.html [3] http://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/trunk/pom.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Changes Plugin version 2.0
+1 from me. I tested the staged plugin with the new/fixed configuration options (columnNames, sortColumnNames, resolutionIds, fixVersionIds, statusIds, priorityIds) in a commons component and it all looks good. Thanks for doing this Dennis :) Niall On Sun, Apr 13, 2008 at 4:59 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Hi, > > We solved 17 issues: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=13722 > > There are still a couple of issues left in JIRA: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1 > > Staging repo: > http://people.apache.org/~dennisl/staging-repository/ > > Staging site (when it has synced): > http://maven.apache.org/plugins/maven-changes-plugin-2.0/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changes Plugin
On Fri, Mar 28, 2008 at 9:38 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Niall Pemberton wrote: > > On Tue, Feb 5, 2008 at 11:20 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > >> I have four issues left on my radar, that I'd like to solve or reject > >> before doing the next release: > > > > Just wondering whether the release is likely soon or not? > > Sorry, I wanted to wait for the release of new plugin parent. > Unfortunately that ran into troubles with the release of > maven-plugin-plugin. Those have now been solved and I'll start a new > vote for plugins parent shortly. Great, thanks Dennis. Niall > > > > Niall > > > > > >> MCHANGES-78 Build a changes report by parsing svn comments > >> - Patch supplied, evaluate whether to include or not > >> > >> MCHANGES-88 NoSuchMethodError with maven 2.0.8 when generating > >> changes-report > >> - I have no clue as to why this happens > >> > >> MCHANGES-96 Change type of path parameters to java.io.File > >> - Patch supplied, need to review before applying it > >> > >> MCHANGES-97 Fix VTL errors > >> - Patch supplied, need to investigate some more before applying it > >> > >> > >> > >> Niall Pemberton wrote: > >> > Is there any chance of a Changes Plugin release? I'd like to use the > >> > JIRA report improvements that have been fixed in the following: > >> > > >> > https://jira.codehaus.org/browse/MCHANGES-92 > >> > https://jira.codehaus.org/browse/MCHANGES-94 > >> > > >> > There are currently 21 outstanding issues: http://tinyurl.com/yvkola > >> > > >> > If someone could assign fix versions for those that are deemed > >> > necessary for the next release, then I will try to help out with > >> > patches. > >> > > >> > Niall > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changes Plugin
On Tue, Feb 5, 2008 at 11:20 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > I have four issues left on my radar, that I'd like to solve or reject > before doing the next release: Just wondering whether the release is likely soon or not? Niall > MCHANGES-78 Build a changes report by parsing svn comments > - Patch supplied, evaluate whether to include or not > > MCHANGES-88 NoSuchMethodError with maven 2.0.8 when generating > changes-report > - I have no clue as to why this happens > > MCHANGES-96 Change type of path parameters to java.io.File > - Patch supplied, need to review before applying it > > MCHANGES-97 Fix VTL errors > - Patch supplied, need to investigate some more before applying it > > > > Niall Pemberton wrote: > > Is there any chance of a Changes Plugin release? I'd like to use the > > JIRA report improvements that have been fixed in the following: > > > > https://jira.codehaus.org/browse/MCHANGES-92 > > https://jira.codehaus.org/browse/MCHANGES-94 > > > > There are currently 21 outstanding issues: http://tinyurl.com/yvkola > > > > If someone could assign fix versions for those that are deemed > > necessary for the next release, then I will try to help out with > > patches. > > > > Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven breaks after last night.
On Thu, Feb 28, 2008 at 7:05 PM, Petar Tahchiev <[EMAIL PROTECTED]> wrote: > > I checked the version of all the maven plugins that are used, and none of the > plugins seems to be updated for the past month. > You can checkout the source of Cactus and try to build it by yourself: > > http://svn.apache.org/repos/asf/jakarta/cactus/trunk/ > > I upload the output of the build process. Actually it turned out that the > build eventually ends, the problem is that it builds actually the source > many times. If you look at the attachment you can see that on line 430 in > stead of continuing with the next uberjar, the build starts again from the > top level pom. This is really strange for me. > > I bet it's a really stupid mistake, but I cannot think of anything to cause > this behaviour. I tried building cactus and got the following error: Missing: -- 1) org.apache.cactus:cactus.core.framework.javaEE.12-13-14:test-jar:tests:1.8.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.cactus -DartifactId=cactus.core.framework.javaEE.12-13-14 -Dversion=1.8.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.cactus -DartifactId=cactus.core.framework.javaEE.12-13-14 -Dversion=1.8.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.cactus:cactus.core.framework.javaEE.13-14:jar:1.8.0-SNAPSHOT 2) org.apache.cactus:cactus.core.framework.javaEE.12-13-14:test-jar:tests:1.8.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.cactus:cactus.core.framework.javaEE.13-14:jar:1.8.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) > Thanks. > > http://www.nabble.com/file/p15743506/outp2 outp2 > > > > > > Niall Pemberton-2 wrote: > > > > On Thu, Feb 28, 2008 at 5:33 PM, Petar Tahchiev <[EMAIL PROTECTED]> > > wrote: > >> > >> Hi guys, > >> > >> my build was working absolutely perfect yesterday. However, today I > >> tried > >> to execute > >> > >> mvn install > >> > >> and the build goes down the submodules, builds them and again starts to > >> build them one by one, and so on infinitely. > >> > >> My project consists of three submodules, each one supposed just to > >> extract > >> using the assembly plugin two other jars in one common folder and then > >> wrap > >> it up again as a whole. > >> > >> Although mvn clean works perfect and cleans the content, any of the "mvn > >> package", "mvn install", "mvn test" doesn't work. I just wanted to ask > >> if > >> anyone knows what could be the reason of this. > > > > Perhaps... > > > > http://www.jroller.com/mrdon/entry/your_build_uses_maven_2 > > > > Niall > > > >> I wouldn't write to the maven-dev list if I don't think that this is a > >> maven-bug. > >> > >> Thank you very much. > >> -- > >> View this message in context: > >> > http://www.nabble.com/Maven-breaks-after-last-night.-tp15741712s177p15741712.html > >> Sent from the Maven Developers mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Maven-breaks-after-last-night.-tp15741712s177p15743506.html > > > Sent from the Maven Developers mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven breaks after last night.
On Thu, Feb 28, 2008 at 5:33 PM, Petar Tahchiev <[EMAIL PROTECTED]> wrote: > > Hi guys, > > my build was working absolutely perfect yesterday. However, today I tried > to execute > > mvn install > > and the build goes down the submodules, builds them and again starts to > build them one by one, and so on infinitely. > > My project consists of three submodules, each one supposed just to extract > using the assembly plugin two other jars in one common folder and then wrap > it up again as a whole. > > Although mvn clean works perfect and cleans the content, any of the "mvn > package", "mvn install", "mvn test" doesn't work. I just wanted to ask if > anyone knows what could be the reason of this. Perhaps... http://www.jroller.com/mrdon/entry/your_build_uses_maven_2 Niall > I wouldn't write to the maven-dev list if I don't think that this is a > maven-bug. > > Thank you very much. > -- > View this message in context: > http://www.nabble.com/Maven-breaks-after-last-night.-tp15741712s177p15741712.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [MNG-3410] Plugin managed versions are ignored
On Feb 19, 2008 5:46 PM, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > On Feb 19, 2008 9:40 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > > On 19-Feb-08, at 9:36 AM, Carlos Sanchez wrote: > > > > > I think you misunderstood. The dependencyManagement is used for > > > project dependencies, fine with that. > > > When you use a plugin no dependencyManagement is applied. The current > > > project depMan shouldn't be applied because it's only for projects, so > > > that's ok. > > > > > > The problem comes when a plugin is built using dependencyManagement to > > > force some dependencies. When that plugin is used, the > > > dependencyManagement of the plugin is ignored, so you run it with > > > different dependencies than the ones you build it with. > > > > > > > So there is no Map used during the plugin's artifact resolution at > > runtime is what you're saying, yes? > > right, and I think it should use the plugin Map that was used during > the plugin build Perhaps related, but I tried specifying a later version of a plugin's dependency and it was ignored: See http://maven.markmail.org/message/km5mlcfsgqlo7le2 Niall > > > > > > On Feb 19, 2008 9:24 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > >> > > >> On 19-Feb-08, at 9:07 AM, Carlos Sanchez wrote: > > >> > > >>> On Feb 19, 2008 7:46 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > > On 18-Feb-08, at 11:54 PM, Carlos Sanchez wrote: > > > > > I'd like to get some feedback in MNG-3410, particularly from > > > John as > > > he has been working on this. > > > > > > If you build and install a plugin with managed versions that > > > affect > > > plugin transitive dependencies, when it's used the dependency > > > management is ignored > > > > > > If the dependency management affects the plugin direct dependecies > > > it > > > works properly because the information is merged. > > > > > > > Dependency management should not affect anything to do with > > plugins. > > If that is happening that is completely wrong. > > > > Dependencies and what plugins use should be completely separate. A > > project's classpath should never affect what is used in a plugin's > > execution. > > > > >>> > > >>> it is, the problem is dependencyManagement in the plugin pom > > >>> > > >> > > >> Then somewhere the Map that is used for managed dependencies is > > >> getting fed into both the project's resolution and the plugin's > > >> resolution and that definitely needs to be separated. Even if we > > >> decide there are certain cases where they should be shared (and I > > >> can't actually think of any real cases except for maybe Antlr vX > > >> generated code needing Antlr vX runtime code which needs to be > > >> aligned) they should be separate so we knowingly combine them if > > >> necessary. > > >> > > >> Problem is if you find that shared Map what are we going to break if > > >> you separate them now? Just thinking aloud. > > >> > > >> > > > > > > > eg. > > > Plugin A depends on jar B that depends on jar C[1.0] > > > A dependencyManagement explicitly forces C[2.0], you build and > > > install > > > using C[2.0] in the classpath > > > > dependencyManagement in your POM or in the plugin's POM? > > >>> > > >>> dependencyManagement in plugin's pom (A) > > >>> > > > > > > > > If you use plugin A in your pom it will be used with C version 1.0 > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Attribute Based POM
On Feb 11, 2008 6:45 AM, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > I've always wanted to see an attribute based POM, so based on Nicolas' > suggestion I killed some time after waking up early this morning to do > it. > > JIRA: http://jira.codehaus.org/browse/MNG-3397 > > Here is a build to try: > http://people.apache.org/~brett/apache-maven-2.0.9-SNAPSHOT-terse-bin.tar.gz > and svn branch: > http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x-terse > > Here are two different files for comparison (it halved the size): > http://svn.apache.org/viewvc/maven/archiva/trunk/pom.xml?content-type=text%2Fplain&view=co > http://svn.apache.org/viewvc/maven/archiva/trunk/pom-4.1.0.xml?content-type=text%2Fplain&view=co How about the option to specify a "dependency" group for dependencies that have the same groupId - something like: Niall > What I did is basically convert all the primitive types in the model > to attributes. I think more could be done (flattening lists, doing the > same for plugin configuration elements), but this gets a big win at > least in the dependencies section for minimal work. > > It should be completely backwards compatible. It detects v4.0.0 and > reads it like it used to (then internally converts to the 4.1.0 Java > model). > > Here's some notes on the implementation so far (again, go easy, I just > whipped this up today and it's not production ready): > - I see this as a stepping stone to the final solution. I've said this > before, but I think the POM should separate the build information from > the project metadata (particularly that stored in the repository). I > think we need to take baby steps towards that though. > - this could feasibly be applied to the settings and profile files too. > - I switched to StAX in the process. This is likely going to introduce > some small quirks we need to iron out (like the hack I added to parse > Trygve's name - why did we ever allow that!) I think ideally we'd use > the Xpp3Reader for 4.0.0 and the StaxReader for 4.1.0 for best > compatibility. This would also fix the problem in that I've just > removed the Xpp3Reader and so some plugins may choke. I'm sure the > release plugin won't be happy, for example. > - There is probably a slight performance overhead in reading v4 POMs > since it repopulates the model twice. I haven't measured it but if > it's an issue we could optimise the reader/converter. It also adds > about 200k to the maven-model JAR. > - It is very close to detecting based on namespace so we could enforce > the use of that instead. > > Enjoy! > > Cheers, > Brett > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changes Plugin
On Feb 6, 2008 2:33 PM, Benjamin Bentmann <[EMAIL PROTECTED]> wrote: > > OK I've put forward a patch for MCHANGES-88 - although its based on > > copying something that works (project info reports) rather than > > understanding what the correct way to handle reports being run > > individually. > > Until r430440 of the maven-reporting-impl, the AbstractMavenReport provided > a default implementation of the execute() method that allowed report mojos > out-of-the-box to run standalone. Now, it just throws an exception and > people start to copy around code from other plugins. Am I missing a point > or is there something going wrong here? Well is worse than that because the AbstractMavenReport reporting impl version that throws the explict MojoExecutionException( "Reporting mojo's can only be called from ReportDocumentRender" ) hasn't yet been released. So when people pick up a newer plexus version (which seems to happen with m2.0.8) then the older AbstractMavenReport reporting impl throws a confusing NoSuchMethod exception which is exactly the problem in MCHANGES-88. Niall > Regards, > > > Benjamin Bentmann > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changes Plugin
I just saw you resolved MCHANGES-96 and MCHANGES-97 - great :) I just had a quick look at MCHANGES-78 - the patch supplied is for a whole new plugin (called svnchangelog-maven-plugin), rather than modifications for maven-changes-plugin, it has no ASF source file headers, "org.apache.codehaus" packaging a francetelecom references in various places - so needs some work to get it ready. Niall On Feb 5, 2008 11:20 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > I have four issues left on my radar, that I'd like to solve or reject > before doing the next release: > > MCHANGES-78 Build a changes report by parsing svn comments > - Patch supplied, evaluate whether to include or not > > MCHANGES-88 NoSuchMethodError with maven 2.0.8 when generating > changes-report > - I have no clue as to why this happens > > MCHANGES-96 Change type of path parameters to java.io.File > - Patch supplied, need to review before applying it > > MCHANGES-97 Fix VTL errors > - Patch supplied, need to investigate some more before applying it > > > Niall Pemberton wrote: > > Is there any chance of a Changes Plugin release? I'd like to use the > > JIRA report improvements that have been fixed in the following: > > > > https://jira.codehaus.org/browse/MCHANGES-92 > > https://jira.codehaus.org/browse/MCHANGES-94 > > > > There are currently 21 outstanding issues: http://tinyurl.com/yvkola > > > > If someone could assign fix versions for those that are deemed > > necessary for the next release, then I will try to help out with > > patches. > > > > Niall > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changes Plugin
On Feb 5, 2008 11:20 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > I have four issues left on my radar, that I'd like to solve or reject > before doing the next release: > > MCHANGES-78 Build a changes report by parsing svn comments > - Patch supplied, evaluate whether to include or not > > MCHANGES-88 NoSuchMethodError with maven 2.0.8 when generating > changes-report > - I have no clue as to why this happens > > MCHANGES-96 Change type of path parameters to java.io.File > - Patch supplied, need to review before applying it > > MCHANGES-97 Fix VTL errors > - Patch supplied, need to investigate some more before applying it OK I've put forward a patch for MCHANGES-88 - although its based on copying something that works (project info reports) rather than understanding what the correct way to handle reports being run individually. If I get a chance I'll try to look at the patches for the other three - and to see if I can help in any way - not sure when I might get round to that though. Niall > Niall Pemberton wrote: > > Is there any chance of a Changes Plugin release? I'd like to use the > > JIRA report improvements that have been fixed in the following: > > > > https://jira.codehaus.org/browse/MCHANGES-92 > > https://jira.codehaus.org/browse/MCHANGES-94 > > > > There are currently 21 outstanding issues: http://tinyurl.com/yvkola > > > > If someone could assign fix versions for those that are deemed > > necessary for the next release, then I will try to help out with > > patches. > > > > Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Changes Plugin
Is there any chance of a Changes Plugin release? I'd like to use the JIRA report improvements that have been fixed in the following: https://jira.codehaus.org/browse/MCHANGES-92 https://jira.codehaus.org/browse/MCHANGES-94 There are currently 21 outstanding issues: http://tinyurl.com/yvkola If someone could assign fix versions for those that are deemed necessary for the next release, then I will try to help out with patches. Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does the apache-jar-resource-bundle follow ASF policy?
On Jan 13, 2008 5:59 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 13-Jan-08, at 5:25 AM, Dennis Lundberg wrote: > > > Hi > > > > As mentioned by Simon on the release thread for maven-jar-plugin, > > there has been discussions [1] over at Apache Commons regarding the > > apache-jar-resource-bundle [2]. > > > > The issue that people have pointed out there, is that the generated > > NOTICE file includes more stuff than they think it should. They are > > of the opinion that it should *not* contain info about the > > dependencies of a project. Only things that are included in the > > distribution (i.e. the jar-file) should be NOTICEd, they say. > > > > Simon also asked on the legal-discuss list for an expert opinion, > > but received no responses. > > > > The documentation about ASF policy on NOTICE files [3] are scarce, > > and doesn't really say anything in the matter, as far as I can see. > > > > IANAL, so I promised that I would take this matter up on maven-dev. > > > > > > [1] http://markmail.org/message/xyzfglktyk56vkse > > [2] > > https://svn.apache.org/repos/asf/maven/resources/tags/apache-jar-resource-bundle-1.3/ > > [3] http://www.apache.org/legal/src-headers.html#notice > > It says that that the notice is used for 3rd party requirements, > what's so unclear about that? > > I wouldn't spend much time on this. Only a lawyer is going to know and > there is always time for us to change anything that's incorrect. > > If you want to look at what is mostly likely correctly look at the > HTTPD notices. Roy Fielding watches over that project and he's the > only non-lawyer at Apache that approaches knowing what a lawyer does > and is the only one here with reliable legal prowess. So anything he > knows would be embodied in the files in the HTTPD project. All the > other jibber jabber by everyone who thinks there are legal problems > generally have no factual basis for their claims and generally don't > know what they are talking about. > > This is a non-issue, we're not going to get into legal trouble for > having more information. And more information is always better so I > would let it be until some lawyer, or Roy, tells us it's categorically > wrong. The real debate is going on on legal-discuss - I asked specifically about the NOTICE file generated for Commons Fileupload here: http://apache.markmail.org/message/zsgfkulbut3bowqu that has only one response, but the other thread (which has hotted up and has Roy involved) on whether they have to be in svn is here: http://apache.markmail.org/message/gyvzsubx7ieg3swt ...and in that thread Roy seems to be saying that they should Personally seems like a fuss about nothing to me, but I would suggest mavenites jump in and fight their corner before banning the remote-resources-plugin becomes policy. Niall > > -- > > Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-source-plugin 2.0.3
+1 Thanks for doing this :) Niall On 4/21/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: Hi, I'd like to release the maven-source-plugin 2.0.3 The staging bits are available here: http://people.apache.org/~snicoll/maven-staging/repo/org/apache/maven/plugins/maven-source-plugin/2.0.3/ The release notes: ** Bug * [MSOURCES-6] - Sources plugin ignores resource includes/excludes * [MSOURCES-12] - size of source jar grows and grows ** Improvement * [MSOURCES-11] - When source plugin is used, it should make sure it is invoked during install Vote open for 72hours. My +1 Stéphane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven-source-plugin] Releasing 2.0.3
ping! Niall On 4/3/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 3 Apr 07, at 1:39 PM 3 Apr 07, Jochen Wiedmann wrote: > Hi, > > now that Maria has applied MSOURCES-14, can this release proceed? > I'll check it with the embedder and a few other projects before I give it a thumbs up. jason. > Thanks, > > Jochen > > > -- > My cats know that I am a loser who goes out for hunting every day > without ever returning as much as a single mouse. Fortunately, I've > got a wife who's a real champ: She leaves the house and returns within > half an hour, carrying whole bags full of meal. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-source-plugin 2.0.3
Any progress on this? Niall On 3/2/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: On 3/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 2 Mar 07, at 7:28 AM 2 Mar 07, Niall Pemberton wrote: > > > ping :-) > > > > I just released a snapshot, do you think you could give it a whirl > quickly? I ran "mvn source:jar" for commons validator with the new snapshot and everything was fine (with a element for something in the root directory). Niall > Jason. > > > On 2/18/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > >> On 2/18/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > >> > > >> > On 18 Feb 07, at 9:32 AM 18 Feb 07, Niall Pemberton wrote: > >> > > >> > > On 2/15/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > >> > >> Yes. I need to check with Jason because it seems he's found a > >> > >> problem meanwhile. > >> > > > >> > > Any news on this - can the release go out (sorry to keep > >> buging you)? > >> > > > >> > > >> > No, I found regressions after the vote. I've fixed most of the > >> > issues, but want to add two more tests and fix the integration > >> > tests. Early next week I'll put it up the vote again. Feel free to > >> > try a snapshot, I deployed it so you can try it which will help me > >> > release it faster. > >> > >> OK thanks - I tried out the the 2.0.4-SNAPSHOT (with Commons > >> Validator) and it built the sources jar fine. > >> > >> Niall > >> > >> > jason. > >> > > >> > > Niall > >> > > > >> > >> I'll keep you posted. > >> > >> > >> > >> Stéphane > >> > >> > >> > >> On 2/15/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > >> > >> > On 2/12/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > >> > >> > > Yes please. > >> > >> > > > >> > >> > > We need to wait a bit more. I'll make sure to send a mail > >> with > >> > >> the vote result. > >> > >> > > >> > >> > Has enough time lapsed yet to declare a result and cut the > >> release? > >> > >> > > >> > >> > Thanks > >> > >> > > >> > >> > Niall > >> > >> > > >> > >> > > Thanks, > >> > >> > > Stéphane > >> > >> > > > >> > >> > > On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > >> > >> > > > Stephane, > >> > >> > > > > >> > >> > > > Would you like me to copy this over to the production > >> > >> repository for > >> > >> > > > the release? > >> > >> > > > > >> > >> > > > Jason. > >> > >> > > > > >> > >> > > > On 11 Feb 07, at 10:42 AM 11 Feb 07, Jason van Zyl wrote: > >> > >> > > > > >> > >> > > > > +1 > >> > >> > > > > > >> > >> > > > > Thanks Stephane, > >> > >> > > > > > >> > >> > > > > Jason. > >> > >> > > > > > >> > >> > > > > On 11 Feb 07, at 5:11 AM 11 Feb 07, Stephane Nicoll > >> wrote: > >> > >> > > > > > >> > >> > > > >> Hi, > >> > >> > > > >> > >> > >> > > > >> This release fixes all known issues. > >> > >> > > > >> > >> > >> > > > >> Release Notes - Maven 2.x Sources Plugin - Version > >> 2.0.3 > >> > >> > > > >> > >> > >> > > > >> ** Bug > >> > >> > > > >>* [MSOURCES-6] - Sources plugin ignores resource > >> > >> includes/excludes > >> > >> > > > >> > >> > >> > > > >> ** Improvement > >> > >> > > > >>* [MSOURCES-11] - When source plugin is used, it > >> > >> sho
Re: [vote] release maven-source-plugin 2.0.3
On 3/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 2 Mar 07, at 7:28 AM 2 Mar 07, Niall Pemberton wrote: > ping :-) > I just released a snapshot, do you think you could give it a whirl quickly? I ran "mvn source:jar" for commons validator with the new snapshot and everything was fine (with a element for something in the root directory). Niall Jason. > On 2/18/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: >> On 2/18/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> > >> > On 18 Feb 07, at 9:32 AM 18 Feb 07, Niall Pemberton wrote: >> > >> > > On 2/15/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: >> > >> Yes. I need to check with Jason because it seems he's found a >> > >> problem meanwhile. >> > > >> > > Any news on this - can the release go out (sorry to keep >> buging you)? >> > > >> > >> > No, I found regressions after the vote. I've fixed most of the >> > issues, but want to add two more tests and fix the integration >> > tests. Early next week I'll put it up the vote again. Feel free to >> > try a snapshot, I deployed it so you can try it which will help me >> > release it faster. >> >> OK thanks - I tried out the the 2.0.4-SNAPSHOT (with Commons >> Validator) and it built the sources jar fine. >> >> Niall >> >> > jason. >> > >> > > Niall >> > > >> > >> I'll keep you posted. >> > >> >> > >> Stéphane >> > >> >> > >> On 2/15/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: >> > >> > On 2/12/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: >> > >> > > Yes please. >> > >> > > >> > >> > > We need to wait a bit more. I'll make sure to send a mail >> with >> > >> the vote result. >> > >> > >> > >> > Has enough time lapsed yet to declare a result and cut the >> release? >> > >> > >> > >> > Thanks >> > >> > >> > >> > Niall >> > >> > >> > >> > > Thanks, >> > >> > > Stéphane >> > >> > > >> > >> > > On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> > >> > > > Stephane, >> > >> > > > >> > >> > > > Would you like me to copy this over to the production >> > >> repository for >> > >> > > > the release? >> > >> > > > >> > >> > > > Jason. >> > >> > > > >> > >> > > > On 11 Feb 07, at 10:42 AM 11 Feb 07, Jason van Zyl wrote: >> > >> > > > >> > >> > > > > +1 >> > >> > > > > >> > >> > > > > Thanks Stephane, >> > >> > > > > >> > >> > > > > Jason. >> > >> > > > > >> > >> > > > > On 11 Feb 07, at 5:11 AM 11 Feb 07, Stephane Nicoll >> wrote: >> > >> > > > > >> > >> > > > >> Hi, >> > >> > > > >> >> > >> > > > >> This release fixes all known issues. >> > >> > > > >> >> > >> > > > >> Release Notes - Maven 2.x Sources Plugin - Version >> 2.0.3 >> > >> > > > >> >> > >> > > > >> ** Bug >> > >> > > > >>* [MSOURCES-6] - Sources plugin ignores resource >> > >> includes/excludes >> > >> > > > >> >> > >> > > > >> ** Improvement >> > >> > > > >>* [MSOURCES-11] - When source plugin is used, it >> > >> should make sure >> > >> > > > >> it is invoked during install >> > >> > > > >> >> > >> > > > >> Revision: 505872 >> > >> > > > >> >> > >> > > > >> The staging bits are available as well: >> > >> > > > >> http://people.apache.org/~snicoll/maven-staging/repo/ >> org/ >> > >> apache/ >> > >> > > > >> maven/plugins/maven-source-plugin/2.0.3/ >> > >> > > > >> >> > >> > > > >> Vote opens for 72hours. >> > >> > > > >> >> > >> > > > >> My +1 >> > >> > > > >> >> > >> > > > >> Thanks, >> > >> > > > >> >> > >> > > > >> Stéphane >> > >> > >> > >> > >> > >> >> - >> > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> > >> > >> >> > >> >> - >> > >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> > >> For additional commands, e-mail: [EMAIL PROTECTED] >> > >> >> > >> >> > > >> > > >> - >> > > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > > For additional commands, e-mail: [EMAIL PROTECTED] >> > > >> > > >> > >> > >> > >> - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-source-plugin 2.0.3
ping :-) On 2/18/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: On 2/18/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 18 Feb 07, at 9:32 AM 18 Feb 07, Niall Pemberton wrote: > > > On 2/15/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > >> Yes. I need to check with Jason because it seems he's found a > >> problem meanwhile. > > > > Any news on this - can the release go out (sorry to keep buging you)? > > > > No, I found regressions after the vote. I've fixed most of the > issues, but want to add two more tests and fix the integration > tests. Early next week I'll put it up the vote again. Feel free to > try a snapshot, I deployed it so you can try it which will help me > release it faster. OK thanks - I tried out the the 2.0.4-SNAPSHOT (with Commons Validator) and it built the sources jar fine. Niall > jason. > > > Niall > > > >> I'll keep you posted. > >> > >> Stéphane > >> > >> On 2/15/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > >> > On 2/12/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > >> > > Yes please. > >> > > > >> > > We need to wait a bit more. I'll make sure to send a mail with > >> the vote result. > >> > > >> > Has enough time lapsed yet to declare a result and cut the release? > >> > > >> > Thanks > >> > > >> > Niall > >> > > >> > > Thanks, > >> > > Stéphane > >> > > > >> > > On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > >> > > > Stephane, > >> > > > > >> > > > Would you like me to copy this over to the production > >> repository for > >> > > > the release? > >> > > > > >> > > > Jason. > >> > > > > >> > > > On 11 Feb 07, at 10:42 AM 11 Feb 07, Jason van Zyl wrote: > >> > > > > >> > > > > +1 > >> > > > > > >> > > > > Thanks Stephane, > >> > > > > > >> > > > > Jason. > >> > > > > > >> > > > > On 11 Feb 07, at 5:11 AM 11 Feb 07, Stephane Nicoll wrote: > >> > > > > > >> > > > >> Hi, > >> > > > >> > >> > > > >> This release fixes all known issues. > >> > > > >> > >> > > > >> Release Notes - Maven 2.x Sources Plugin - Version 2.0.3 > >> > > > >> > >> > > > >> ** Bug > >> > > > >>* [MSOURCES-6] - Sources plugin ignores resource > >> includes/excludes > >> > > > >> > >> > > > >> ** Improvement > >> > > > >>* [MSOURCES-11] - When source plugin is used, it > >> should make sure > >> > > > >> it is invoked during install > >> > > > >> > >> > > > >> Revision: 505872 > >> > > > >> > >> > > > >> The staging bits are available as well: > >> > > > >> http://people.apache.org/~snicoll/maven-staging/repo/org/ > >> apache/ > >> > > > >> maven/plugins/maven-source-plugin/2.0.3/ > >> > > > >> > >> > > > >> Vote opens for 72hours. > >> > > > >> > >> > > > >> My +1 > >> > > > >> > >> > > > >> Thanks, > >> > > > >> > >> > > > >> Stéphane > >> > > >> > > >> - > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > >> > > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-source-plugin 2.0.3
On 2/18/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 18 Feb 07, at 9:32 AM 18 Feb 07, Niall Pemberton wrote: > On 2/15/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: >> Yes. I need to check with Jason because it seems he's found a >> problem meanwhile. > > Any news on this - can the release go out (sorry to keep buging you)? > No, I found regressions after the vote. I've fixed most of the issues, but want to add two more tests and fix the integration tests. Early next week I'll put it up the vote again. Feel free to try a snapshot, I deployed it so you can try it which will help me release it faster. OK thanks - I tried out the the 2.0.4-SNAPSHOT (with Commons Validator) and it built the sources jar fine. Niall jason. > Niall > >> I'll keep you posted. >> >> Stéphane >> >> On 2/15/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: >> > On 2/12/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: >> > > Yes please. >> > > >> > > We need to wait a bit more. I'll make sure to send a mail with >> the vote result. >> > >> > Has enough time lapsed yet to declare a result and cut the release? >> > >> > Thanks >> > >> > Niall >> > >> > > Thanks, >> > > Stéphane >> > > >> > > On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> > > > Stephane, >> > > > >> > > > Would you like me to copy this over to the production >> repository for >> > > > the release? >> > > > >> > > > Jason. >> > > > >> > > > On 11 Feb 07, at 10:42 AM 11 Feb 07, Jason van Zyl wrote: >> > > > >> > > > > +1 >> > > > > >> > > > > Thanks Stephane, >> > > > > >> > > > > Jason. >> > > > > >> > > > > On 11 Feb 07, at 5:11 AM 11 Feb 07, Stephane Nicoll wrote: >> > > > > >> > > > >> Hi, >> > > > >> >> > > > >> This release fixes all known issues. >> > > > >> >> > > > >> Release Notes - Maven 2.x Sources Plugin - Version 2.0.3 >> > > > >> >> > > > >> ** Bug >> > > > >>* [MSOURCES-6] - Sources plugin ignores resource >> includes/excludes >> > > > >> >> > > > >> ** Improvement >> > > > >>* [MSOURCES-11] - When source plugin is used, it >> should make sure >> > > > >> it is invoked during install >> > > > >> >> > > > >> Revision: 505872 >> > > > >> >> > > > >> The staging bits are available as well: >> > > > >> http://people.apache.org/~snicoll/maven-staging/repo/org/ >> apache/ >> > > > >> maven/plugins/maven-source-plugin/2.0.3/ >> > > > >> >> > > > >> Vote opens for 72hours. >> > > > >> >> > > > >> My +1 >> > > > >> >> > > > >> Thanks, >> > > > >> >> > > > >> Stéphane >> > >> > >> - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-source-plugin 2.0.3
On 2/15/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: Yes. I need to check with Jason because it seems he's found a problem meanwhile. Any news on this - can the release go out (sorry to keep buging you)? Niall I'll keep you posted. Stéphane On 2/15/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > On 2/12/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > > Yes please. > > > > We need to wait a bit more. I'll make sure to send a mail with the vote result. > > Has enough time lapsed yet to declare a result and cut the release? > > Thanks > > Niall > > > Thanks, > > Stéphane > > > > On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > Stephane, > > > > > > Would you like me to copy this over to the production repository for > > > the release? > > > > > > Jason. > > > > > > On 11 Feb 07, at 10:42 AM 11 Feb 07, Jason van Zyl wrote: > > > > > > > +1 > > > > > > > > Thanks Stephane, > > > > > > > > Jason. > > > > > > > > On 11 Feb 07, at 5:11 AM 11 Feb 07, Stephane Nicoll wrote: > > > > > > > >> Hi, > > > >> > > > >> This release fixes all known issues. > > > >> > > > >> Release Notes - Maven 2.x Sources Plugin - Version 2.0.3 > > > >> > > > >> ** Bug > > > >>* [MSOURCES-6] - Sources plugin ignores resource includes/excludes > > > >> > > > >> ** Improvement > > > >>* [MSOURCES-11] - When source plugin is used, it should make sure > > > >> it is invoked during install > > > >> > > > >> Revision: 505872 > > > >> > > > >> The staging bits are available as well: > > > >> http://people.apache.org/~snicoll/maven-staging/repo/org/apache/ > > > >> maven/plugins/maven-source-plugin/2.0.3/ > > > >> > > > >> Vote opens for 72hours. > > > >> > > > >> My +1 > > > >> > > > >> Thanks, > > > >> > > > >> Stéphane > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-source-plugin 2.0.3
On 2/12/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: Yes please. We need to wait a bit more. I'll make sure to send a mail with the vote result. Has enough time lapsed yet to declare a result and cut the release? Thanks Niall Thanks, Stéphane On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > Stephane, > > Would you like me to copy this over to the production repository for > the release? > > Jason. > > On 11 Feb 07, at 10:42 AM 11 Feb 07, Jason van Zyl wrote: > > > +1 > > > > Thanks Stephane, > > > > Jason. > > > > On 11 Feb 07, at 5:11 AM 11 Feb 07, Stephane Nicoll wrote: > > > >> Hi, > >> > >> This release fixes all known issues. > >> > >> Release Notes - Maven 2.x Sources Plugin - Version 2.0.3 > >> > >> ** Bug > >>* [MSOURCES-6] - Sources plugin ignores resource includes/excludes > >> > >> ** Improvement > >>* [MSOURCES-11] - When source plugin is used, it should make sure > >> it is invoked during install > >> > >> Revision: 505872 > >> > >> The staging bits are available as well: > >> http://people.apache.org/~snicoll/maven-staging/repo/org/apache/ > >> maven/plugins/maven-source-plugin/2.0.3/ > >> > >> Vote opens for 72hours. > >> > >> My +1 > >> > >> Thanks, > >> > >> Stéphane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven-source-plugin] Releasing 2.0.3
On 2/11/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: Hi, On 2/11/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > All the issue tickets for the maven sources plugin are resolved: > >http://jira.codehaus.org/browse/MSOURCES > > Is there likely to be a 2.0.3 release soon? > Yes, I'll handle this. Great and thanks! Niall Cheers, Stéphane > thx > > Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven-source-plugin] Releasing 2.0.3
All the issue tickets for the maven sources plugin are resolved: http://jira.codehaus.org/browse/MSOURCES Is there likely to be a 2.0.3 release soon? thx Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1725) Enable User Templates in XDOC plugin
[ http://jira.codehaus.org/browse/MAVEN-1725?page=all ] Niall Pemberton updated MAVEN-1725: --- Attachment: xdoc-user-template2.patch Woops, sorry missed a bit of the change when cut & pasting - attaching new patch version > Enable User Templates in XDOC plugin > > > Key: MAVEN-1725 > URL: http://jira.codehaus.org/browse/MAVEN-1725 > Project: Maven > Type: New Feature > Reporter: Niall Pemberton > Priority: Minor > Attachments: xdoc-user-template.patch, xdoc-user-template2.patch > > > It would be useful to allow custom user templates to be specified in the xdoc > plugin, as perr this thread: > http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg69686.html > I suggest allowing a "user template directory" to be specified and the xdoc > plugin check for the existence of a user template there. > Attaching a patch to do this (I tested these changes by hacking my cached > version 1.9.2 of the xdoc plugin, but not against the current svn version). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1725) Enable User Templates in XDOC plugin
Enable User Templates in XDOC plugin Key: MAVEN-1725 URL: http://jira.codehaus.org/browse/MAVEN-1725 Project: Maven Type: New Feature Reporter: Niall Pemberton Priority: Minor Attachments: xdoc-user-template.patch It would be useful to allow custom user templates to be specified in the xdoc plugin, as perr this thread: http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg69686.html I suggest allowing a "user template directory" to be specified and the xdoc plugin check for the existence of a user template there. Attaching a patch to do this (I tested these changes by hacking my cached version 1.9.2 of the xdoc plugin, but not against the current svn version). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPCHANGELOG-74) changelog plugin creates wrong links for Subversion repositories
[ http://jira.codehaus.org/browse/MPCHANGELOG-74?page=comments#action_46985 ] Niall Pemberton commented on MPCHANGELOG-74: A workaround for this issue is to set the repository url to the root ASF one - that causes changelog to generate "good links": http://svn.apache.org/viewcvs.cgi The only problem then is the link on the generated "Source Repository" page just points to the whole of ASF, rather than your particular project. You can get round this by including a custom "cvs-usage.xml" document in the "xdocs" directory. Just out of interest the "change log" report for the maven-changelog-plugin is also currently suffering from this issue: http://maven.apache.org/reference/plugins/changelog/changelog-report.html > changelog plugin creates wrong links for Subversion repositories > > > Key: MPCHANGELOG-74 > URL: http://jira.codehaus.org/browse/MPCHANGELOG-74 > Project: maven-changelog-plugin > Type: Bug > Versions: 1.8.2 > Reporter: Henning Schmiedehausen > Attachments: changelog-report.html > > > The maven file-activity plugin creates wrong links at > docs/file-activity-report.html. > project.xml > > > scm:svn:http://svn.apache.org/repos/asf/jakarta/turbine/core/branches/TURBINE_2_3_BRANCH > > scm:svn:https://svn.apache.org/repos/asf/jakarta/turbine/core/branches/TURBINE_2_3_BRANCH > > http://svn.apache.org/viewcvs/jakarta/turbine/core/branches/TURBINE_2_3_BRANCH/ > > results in the attached changelog-report.html file where the links into the > SCM look like this: > http://svn.apache.org/viewcvs/jakarta/turbine/core/branches/TURBINE_2_3_BRANCH//jakarta/turbine/core/branches/TURBINE_2_3_BRANCH/project.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPCHANGELOG-58) allow showing last X revisions of a file instead of dates
[ http://jira.codehaus.org/browse/MPCHANGELOG-58?page=all ] Niall Pemberton updated MPCHANGELOG-58: --- Attachment: SvnBug752ChangeLogFactory.java ChangeLogFactory implementation for Bug 752 > allow showing last X revisions of a file instead of dates > - > > Key: MPCHANGELOG-58 > URL: http://jira.codehaus.org/browse/MPCHANGELOG-58 > Project: maven-changelog-plugin > Type: New Feature > Reporter: Brett Porter > Attachments: SvnBug752ChangeLogFactory.java, SvnBug752ChangeLogGenerator.java > > > currently, dates based logs can be broken on some repositories where multiple > CVS imports have occured (eg, the Apache SVN repository). > Add an option to just show the last 20 changes instead of 30 days. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPCHANGELOG-58) allow showing last X revisions of a file instead of dates
[ http://jira.codehaus.org/browse/MPCHANGELOG-58?page=all ] Niall Pemberton updated MPCHANGELOG-58: --- Attachment: SvnBug752ChangeLogGenerator.java ChangeLogGenerator implementation which gets round the issue of Bug 752 in Subversion: http://subversion.tigris.org/issues/show_bug.cgi?id=752 This version gets all log entries using command "svn log -v" and then filters out ChangeLogEntry's that are not within the specified timescale. > allow showing last X revisions of a file instead of dates > - > > Key: MPCHANGELOG-58 > URL: http://jira.codehaus.org/browse/MPCHANGELOG-58 > Project: maven-changelog-plugin > Type: New Feature > Reporter: Brett Porter > Attachments: SvnBug752ChangeLogGenerator.java > > > currently, dates based logs can be broken on some repositories where multiple > CVS imports have occured (eg, the Apache SVN repository). > Add an option to just show the last 20 changes instead of 30 days. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
