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 "Brett Porter (JIRA)" <ji...@apache.org> on 2013/03/02 08:41:12 UTC

[jira] [Resolved] (NPANDAY-579) Ability to copy artifacts into the local repository as part of the import process

     [ https://issues.apache.org/jira/browse/NPANDAY-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter resolved NPANDAY-579.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0-incubating
         Assignee: Brett Porter
    
> Ability to copy artifacts into the local repository as part of the import process
> ---------------------------------------------------------------------------------
>
>                 Key: NPANDAY-579
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-579
>             Project: NPanday
>          Issue Type: New Feature
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>             Fix For: 1.5.0-incubating
>
>
> It is quite common for Visual Studio projects to result in a number of references to the GAC, or to system paths, which make for non-portable projects. It would be useful for the import to have an option to copy artifacts to the local repository, and then use normal Maven repository references. In combination with NPANDAY-578 this gives you all the artifacts arranged in a way that can be loaded into a remote repository.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira