[
https://issues.apache.org/jira/browse/NPANDAY-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965678#action_12965678
]
Paul G commented on NPANDAY-353:
--------------------------------
Hi Brett. I'm looking at snapshot handling for now as this will be a common
use-case for us.
Ok - I've done some further digging. I followed the "Debugging the Visual
Studio Add-in" guide to see what was going on in there, and found the following
issues:
1. When I built the DLLs from the 1.2.1 source I found that the snapshot resync
between two projects running on the same PC (i.e. using local repo) works fine.
Not sure why there's a different behaviour because I installed the 1.2.1 from
the MSI installer image.
2. There are two reasons for the 'fails immediately' behaviour shown above:
a) I didn't have a 'mirrors' section in my settings.xml, causing
ProjectImporterEngine's Reference.cs to throw an NPE (line 283 'foreach (Mirror
mirror in settings.mirrors)'). For now I've just added an empty section.
b) In the same file at line 292 the repo 'http://repo1.maven.org/maven2' is
hard-wired be added to the list of repos to lookup. As soon as an attempt is
made to access this site I get a network access issue (because of our network
config). In my opinion this should not be forced into the repos collection. In
my case I want to use archiva (and only archiva) as my artifact source. For now
I've just commented this line out and that problem is resolved.
So now I seem to have the basic features working. Any chance of getting these
worked into the next release?
> 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.
