[
https://jira.codehaus.org/browse/WAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342247#comment-342247
]
David Ireland commented on WAGON-409:
-------------------------------------
I've seen 409, which was closed as a result of another user affectively telling
the reporter to not use webdav, which is certainly a universal way to avoid
bugs in this project. Neither party seems to be aware of this.
I've also seen this bug reported against 2.5 in various forums.
I can't help noticing you seem to have excluded the needed dependency a couple
of times in the pom.xml, saying it's added back below. It's not added back
below.
In fact, adding this:
<dependency>
<artifactId>commons-logging</artifactId>
<groupId>commons-logging</groupId>
<version>1.1.3</version>
</dependency>
To wagon-webdav-jackrabbit-2.6.pom in my local repo fixes the problem.
> Wagon-webdav-jackrabbit throws Class Not Found Exception.
> ---------------------------------------------------------
>
> Key: WAGON-409
> URL: https://jira.codehaus.org/browse/WAGON-409
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-webdav
> Affects Versions: 2.5, 2.6
> Environment: Maven 3.1.1, fedora, jenkins
> Reporter: Eric Barboni
> Priority: Critical
> Attachments: log.txt
>
>
> I try to upgrade to the 2.6 version of jackrabbit wagon on a previoulsy
> working project (with version 2.4).
> During instantiation of MultiThreadedHttpConnectionManager the LogFactory
> class is not available and break deploy.
> The removal of dependencies wagon-http-shared after 2.4 seems to be the cause
> of the issue. http-shared was providing commons logging as transitive
> dependencies ofr jackrabbit.
> Best Regards
> I copy paste extract from the jenkins logs in attachement.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
