[
http://jira.codehaus.org/browse/MNG-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-4279.
---------------------------
Resolution: Fixed
added code to check that the protocol-provider hint exists before blindly
passing it back. If it doesn't exist, simply fall back to the protocol as the
hint.
> wagon provider selection should fail gracefully and use protocol for roleHint
> if protocol-provider roleHint isn't available.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-4279
> URL: http://jira.codehaus.org/browse/MNG-4279
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.2.1
>
>
> Currently, if the server section of the settings.xml uses wagonProvider to
> set a provider suffix, that provider may apply to multiple different
> repository definitions.
> If the user specifies a repository with protocol == http and provider ==
> httpclient for artifact resolution using a server id of 'foo', then configure
> a distribution repository with protocol == scp, the provider == httpclient
> will be applied to this distribution repo, and result in an error like this:
> {noformat}
> Component descriptor cannot be found in the component repository:
> org.apache.maven.wagon.Wagonscp-httpclient.
> {noformat}
> Obviously, this will never work. In these cases, ideally different server IDs
> should be used. However, if not then Maven should fallback gracefully to a
> roleHint of 'scp'.
--
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
