You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/04/28 04:01:45 UTC

[jira] Commented: (MNG-4133) ssh-external wagon can not be overridden on its own

    [ http://jira.codehaus.org/browse/MNG-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174404#action_174404 ] 

John Casey commented on MNG-4133:
---------------------------------

This seems to indicate a broader problem with scm, wagon, etc. providers. I can shade the http shared stuff and the ssh common scm stuff...what else do we need to think about on this front? 

Also, what does the failure look like when the extension loading mechanism comes apart? I'm happy to take a look, but I'm not entirely sure I know what to look for...

> ssh-external wagon can not be overridden on its own
> ---------------------------------------------------
>
>                 Key: MNG-4133
>                 URL: http://jira.codehaus.org/browse/MNG-4133
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Class Loading
>    Affects Versions: 2.1.0
>            Reporter: Brett Porter
>             Fix For: 2.1.1
>
>
> when a project only overrides the ssh-external wagon, it causes the wagon-ssh that is built in to fail to load (probably because of a classloading conflict with ssh-common). See the linked issue for details.
> A couple of fixes are needed here:
> - don't crash the entire extension loading mechanism because one extension failed to load
> - possibly shade the common ssh JAR in the core so it doesn't cause the conflict in the first place.

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