[jira] Commented: (NPANDAY-353) Inconsistent use of repository and GAC when using Archiva

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

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

Brett Porter commented on NPANDAY-353:
--------------------------------------

it sounds correct, and this definitely works - I'm not sure which piece is missing in your description.

are the versions involved always snapshots?

> Inconsistent use of repository and GAC when using Archiva
> ---------------------------------------------------------
>
>                 Key: NPANDAY-353
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-353
>             Project: NPanday
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: Windows
>            Reporter: Paul G
>
> I've created a Visual Studio project A (which generates a class library) and project B (a console app which depends on project A's library). If I run 'install' goal for project A then I see the library in the "%M2_HOME%/repository" area as expected. Since I have archiva configured I then try running 'deploy' for project A and all is well: the library DLL is written to archiva correctly. I then create a new version of library A and deploy to archiva, but on a different PC to where I'm working on project B. I then update project B's dependency entry for project A's library to reference the new version. When I try 'resync references' for project B it fails immediately and does not attempt to pull the library in from Archiva. However if I run "maven install" from the command shell for project B then it does pull the library from Archiva, but strangely it get's written to the "%M2_HOME%/uac/gac_msil" area instead of the "%M2_HOME%/repository" area.
> Unfortunately for large team development this makes NPanday currently not suitable. Am I using it incorrectly or is this a bug?

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