You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Paul G (JIRA)" <ji...@apache.org> on 2010/12/01 15:08:11 UTC

[jira] Commented: (NPANDAY-355) Addin 'resync references' feature hard-wires ''http://repo1.maven.org/maven2' as remote repository causing network security violations.

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

Paul G commented on NPANDAY-355:
--------------------------------

Forgot to mention, this is hard-wired in ProjectImporterEngine's Reference.cs line 292

> Addin 'resync references' feature hard-wires ''http://repo1.maven.org/maven2' as remote repository causing network security violations.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NPANDAY-355
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-355
>             Project: NPanday
>          Issue Type: Bug
>          Components: Visual Studio Add-in
>    Affects Versions: 1.2.1
>         Environment: Windows
>            Reporter: Paul G
>
> If the settings.xml file specifies the remote repositories to be uses, there is no reason for the Addin code to specify any additional repos. This also messes up the usage of managed repositories like Archiva (since some download may not actually originate from there but instead come directly from the hard-wired repo source).
> Where a devepment network is locked down for security purposes, this causes the resync to fail with a security error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.