o there is a subtle realm problem with plexus and under certain conditions (release deploys) the wagon manager used to populate auth info is not the same as used by the wagon manager. this is fixed in subsequent releases of plexus but i'm not testing everything again so i'm using a static map as a work around. when alpha-1 is released i'll bump the version of plexus and test again.

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@730868 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2009-01-02 23:35:29 +00:00
parent 6a3afa1c46
commit ab9347bc76
1 changed files with 5 additions and 3 deletions

View File

@ -91,7 +91,7 @@ public class DefaultWagonManager
// attached to ArtifactRepository before the method is called (so AR would be composed of WR, not inherit it)
private Map<String,ProxyInfo> proxies = new HashMap<String,ProxyInfo>();
private Map<String,AuthenticationInfo> authenticationInfoMap = new HashMap<String,AuthenticationInfo>();
private static Map<String,AuthenticationInfo> authenticationInfoMap = new HashMap<String,AuthenticationInfo>();
private Map<String,RepositoryPermissions> serverPermissionsMap = new HashMap<String,RepositoryPermissions>();
@ -239,7 +239,9 @@ private void putRemoteFile( ArtifactRepository repository,
getLogger().debug( "not adding permissions to wagon connection" );
}
wagon.connect( artifactRepository, getAuthenticationInfo( repository.getId() ), new ProxyInfoProvider()
AuthenticationInfo authenticationInfo = getAuthenticationInfo( repository.getId() );
wagon.connect( artifactRepository, authenticationInfo, new ProxyInfoProvider()
{
public ProxyInfo getProxyInfo( String protocol )
{