From npanday-commits-return-339-apmail-incubator-npanday-commits-archive=incubator.apache.org@incubator.apache.org Wed Dec 01 14:15:33 2010 Return-Path: Delivered-To: apmail-incubator-npanday-commits-archive@minotaur.apache.org Received: (qmail 22057 invoked from network); 1 Dec 2010 14:15:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Dec 2010 14:15:33 -0000 Received: (qmail 25912 invoked by uid 500); 1 Dec 2010 14:15:33 -0000 Delivered-To: apmail-incubator-npanday-commits-archive@incubator.apache.org Received: (qmail 25875 invoked by uid 500); 1 Dec 2010 14:15:32 -0000 Mailing-List: contact npanday-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: npanday-dev@incubator.apache.org Delivered-To: mailing list npanday-commits@incubator.apache.org Received: (qmail 25865 invoked by uid 99); 1 Dec 2010 14:15:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Dec 2010 14:15:32 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Dec 2010 14:15:31 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB1EFBVh010573 for ; Wed, 1 Dec 2010 14:15:11 GMT Message-ID: <3467829.46501291212911031.JavaMail.jira@thor> Date: Wed, 1 Dec 2010 09:15:11 -0500 (EST) From: "Paul G (JIRA)" To: npanday-commits@incubator.apache.org Subject: [jira] Commented: (NPANDAY-353) Inconsistent use of repository and GAC when using Archiva In-Reply-To: <6237895.21151291108271193.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NPANDAY-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965685#action_12965685 ] Paul G commented on NPANDAY-353: -------------------------------- Next I checked to see if it would spot snapshot updates that have been posted to archiva from a different PC - unfortunately it doesn't. The VisualStudio.Addin's ReferenceManager.cs is a bit over-simplistic: it simply checks for the presence of a snapshot artifact file in the local repo, and if it's present it copies it to the project's reference folder. No attempt to check the remote snapshot state :( I'll start putting a hack together for this. Please let me know if there's already a fix for this. Thanks > 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.