[jira] Updated: (NMAVEN-140) Make add remote artifact feature of Nmaven more robust, improve parsing of remote artifacts

["jan ancajas (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/NMAVEN-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jan ancajas updated NMAVEN-140:
-------------------------------

    Attachment: NMAVEN-140v2.patch

updated patch to fix the error..

also included in the patch to  handle errors for :
a.)  adding an artifact in VS but it is listed in pom.xml
b.)  artifact that is added twice
c.)  removing an artifact in VS  but it's missing in pom.xml
d.)  adding an artifact for non-standard nmaven directory structure.

> Make  add remote artifact feature of Nmaven more robust, improve parsing of remote artifacts
> --------------------------------------------------------------------------------------------
>
>                 Key: NMAVEN-140
>                 URL: http://jira.codehaus.org/browse/NMAVEN-140
>             Project: NMaven
>          Issue Type: Improvement
>          Components: Visual Studio Integration
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>             Fix For: 0.14 (Unreleased)
>
>         Attachments: NMAVEN-139-140.patch, NMAVEN-140v2.patch
>
>
> i observed the ff:
> 1. when a repository is offline or remote artifact is unreachable, using the add remote artifact feature will cause the VS to crash
> 2. if the html  of the repository has this structure : <baseurl>/./NUnit/./NUnit.Framework/./2.2.8.0/./NUnit.Framework-2.2.8.0.dll , dependency info generated is incorrect
> 3. the code is expecting a "maven2"-ending-base-url of your repository, not  following "maven2"  will cause the dependency info to be incorrect /  VS crash.

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