[jira] [Commented] (NPANDAY-543) Resync References doesn´t update dependencies from remote repositories with LDAP verification

["Brett Porter (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NPANDAY-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105079#comment-14105079 ] 

Brett Porter commented on NPANDAY-543:
--------------------------------------

Sorry, this isn't yet supported. While a user/pass is prompted in the add maven artifact dialog, it is not stored in the servers section automatically, and that section is not used by the resync code to set the credentials when synchronising.

Those changes might be straightforward, but supporting the encrypted plugins may be more difficult as it would need to emulate the same logic as Maven itself.

> Resync References doesn´t update dependencies from remote repositories with LDAP verification
> ---------------------------------------------------------------------------------------------
>
>                 Key: NPANDAY-543
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-543
>             Project: NPanday
>          Issue Type: Bug
>          Components: Visual Studio Add-in
>    Affects Versions: 1.4-incubating
>         Environment: Archiva 1.3.5.,
> NPanday 1.4-incubating,
> Visual studion 2010
> Maven 3.0.3
>            Reporter: Jiri Pergl
>            Assignee: Brett Porter
>            Priority: Blocker
>
> Steps:
> 1. Add references using "Add Maven Artifact" from the menu(VS) or direct in the project pom.
> 2. Update the configuration in the settings.xml.
>    - I insert to the configuration in the setting.xml this snippet:
> ... 
> <server>
>       <id>npanday.repo.0</id>
>       <username>{LDAP user name}</username>
>       <password>{encrypted password}</password>
>  </server>
> ...
> 3. Refresh references using "Resync References" from the menu(VS).
> After action I see message "Download Failed The remote server returned an error: (401) Unauthorized." 
> I found out that Archiva is contacted without LDAP parameters in the communication between Archiva and local machine. If I try the goal "deploy" on the simple project, the communication is ok.



--
This message was sent by Atlassian JIRA
(v6.2#6252)