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

Lars Corneliussen commented on NPANDAY-322:
-------------------------------------------

I still get an exception, if the artifact is not deployed to any of the remote 
repositories. That's not correct, is it?

Both Resync and Resync from Local Repo should work in that case, right?

Just that Resync from Local Repo should give local snapshots precedence over 
remote ones, even if the remote ones are newer. Right, too?
                
> Resync Reference doesn't update SNAPSHOT artifact from local repository that 
> already exist in .references folder
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: NPANDAY-322
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-322
>             Project: NPanday
>          Issue Type: Bug
>          Components: Visual Studio Add-in
>    Affects Versions: 1.4-incubating
>            Reporter: Dmitry L
>            Assignee: Lars Corneliussen
>            Priority: Minor
>             Fix For: 1.2.1, 1.4.1-incubating
>
>         Attachments: ArtifactUtils.cs, Connect.cs, 
> NPANDAY-322_and_NPANDAY-476.diff, ReferenceManager.cs, 
> TEST-npanday.its.IntegrationTestSuite.xml, 
> npanday.its.IntegrationTestSuite.txt
>
>
> Steps:
> 1. Install Library1 into local maven repo
> 2. Add Library1 as dependency using Resync Reference to ProjectA (it will be 
> copied into .references folder)
> 3. Update and reinstall Library1 into local maven repo
> 4. Invoke Resync Reference for ProjectA
> 5. Error: Library1 won't be updated in .references folder
> Expected: newer version (in terms of file timestamp) of Library1 (if any) 
> should be copied into .references folder from local maven repo during Resync 
> Reference
> Issue exist in trunk r59731

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to