[ 
http://jira.codehaus.org/browse/MNG-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100735
 ] 

Calin Medianu commented on MNG-2900:
------------------------------------

Hi,

Thanks again for looking into it. Indeed, in 2.0.7 this issue is fixed and 
another issue has surfaced. In 2.0.6 is is NOT fixed. I said on TSS that this 
bug was not fixed in 2.0.6, which is true.

My comment on TSS was unkind and I'm sorry for that. The reason was to draw 
attention to the comment from Brill Pappin - [07/May/07 12:04 PM ]  which was 
ignored for 2 months as well as the frustration from having to support a 
co-worker that decided to upgrade from 2.0.4 to 2.0.6  and DAV stopped working 
for her. in 2.0.4 dav is working from the command line with the extra jars in 
maven/lib, in 2.0.6 it cannot find the org/codehaus/plexus/util/StringUtils

I am actually a promoter of maven2 in my organization...

Thanks,

Calin

> Extensions that have no declared dependency on plexus-utils yet need it at 
> runtime will fail.
> ---------------------------------------------------------------------------------------------
>
>                 Key: MNG-2900
>                 URL: http://jira.codehaus.org/browse/MNG-2900
>             Project: Maven 2
>          Issue Type: Bug
>            Reporter: Jason van Zyl
>            Assignee: Jason van Zyl
>             Fix For: 2.0.6
>
>
> This is happening with the WebDAV Wagon:
>     java.lang.NoClassDefFoundError: org/codehaus/plexus/util/StringUtils
>         at 
> org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java:192)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:237)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:153)
>         at 
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>         at 
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

-- 
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

        

Reply via email to