You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jan ancajas (JIRA)" <ji...@codehaus.org> on 2008/06/05 11:58:54 UTC

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

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

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

    Attachment: NMAVEN-139-140.patch

attached patch. I included the patch in 139  since  the same file is affected in the fix.   Thanks :)

> 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
>            Reporter: jan ancajas
>         Attachments: NMAVEN-139-140.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