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]
