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

Stoyan Damov updated NPANDAY-322:
---------------------------------

    Attachment: Connect.cs
                ArtifactUtils.cs
                ReferenceManager.cs
                NPANDAY-322_and_NPANDAY-476.diff

{{ReferenceManager.cs}} and {{ArtifactUtils.cs}} fix NPANDAY-322.

{{ReferenceManager.cs}} also has the code necessary to implement NPANDAY-476.

I've also attached {{Connect.cs}} which does implement NPANDAY-476.

This is my first contribution so I'm not really sure whether I can propose a 
change set for two issues at a time. Happy to split the changeset in two if 
necessary.

I'm going to put a separate comment explaining all changes.
                
> 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
>            Priority: Minor
>             Fix For: 1.2.1
>
>         Attachments: ArtifactUtils.cs, Connect.cs, 
> NPANDAY-322_and_NPANDAY-476.diff, ReferenceManager.cs
>
>
> 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