incubator-npanday-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Corneliussen (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NPANDAY-322) Resync Reference doesn't update SNAPSHOT artifact from local repository that already exist in .references folder
Date Thu, 03 Nov 2011 12:05:32 GMT

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

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

I can't see, why File.Copy has been changed..
Who made the change? Ask the committer why he made this change..

Also I really, sorry, hate the silent-catches all over NPanday. This is an error - not showing
it, doesn't make it any better.
                
> 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
>
>
> 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

        

Mime
View raw message