[
http://jira.codehaus.org/browse/MNG-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100738
]
Jason van Zyl commented on MNG-2900:
------------------------------------
We appreciate that, and I know people get frustrated but we're just like every
other development shop that has problems ... ours is just spread out all over
the world and we have very few dedicated resources. Also, that a comment isn't
made in JIRA doesn't mean we're not looking at something. We could probably
comment better, or mark issues as in progress but I looked at the issue pretty
soon after it was report though it did take me a few weeks to getting around to
fixing it.
> 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
