You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Daniel Dekany (JIRA)" <ji...@apache.org> on 2009/03/09 13:22:51 UTC

[jira] Created: (IVY-1044) retrieve doesn't retrive files if the current one is more recent

retrieve doesn't retrive files if the current one is more recent
----------------------------------------------------------------

                 Key: IVY-1044
                 URL: https://issues.apache.org/jira/browse/IVY-1044
             Project: Ivy
          Issue Type: Bug
          Components: Ant
    Affects Versions: 2.0
         Environment: Win XP, J2SE 1.6.0_11-b03
            Reporter: Daniel Dekany


The "retrieve" task will not retrieve files (artifacts) whose file modification date is greater than of the file in the repository (in the "resolver"), not even if sync="true". This way the target directory goes out of sync if (a) the module is downgraded in the repository or (b) the developer has overwritten the artifact manually when experiencing with something. Thus the only way to keep the target directory in sync is deleting it before retrieving, but of course that means suboptimal performance, and makes sync="true" useless anyway. Simply, a file should be retrieved if the date (or size!) is *different* than in the repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-1044) retrieve doesn't retrive files if the current one is more recent

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene updated IVY-1044:
-------------------------------

         Assignee: Maarten Coene
    Fix Version/s: 2.2.0-RC1
      Component/s: Core

> retrieve doesn't retrive files if the current one is more recent
> ----------------------------------------------------------------
>
>                 Key: IVY-1044
>                 URL: https://issues.apache.org/jira/browse/IVY-1044
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant, Core
>    Affects Versions: 2.0
>         Environment: Win XP, J2SE 1.6.0_11-b03
>            Reporter: Daniel Dekany
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> The "retrieve" task will not retrieve files (artifacts) whose file modification date is greater than of the file in the repository (in the "resolver"), not even if sync="true". This way the target directory goes out of sync if (a) the module is downgraded in the repository or (b) the developer has overwritten the artifact manually when experiencing with something. Thus the only way to keep the target directory in sync is deleting it before retrieving, but of course that means suboptimal performance, and makes sync="true" useless anyway. Simply, a file should be retrieved if the date (or size!) is *different* than in the repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-1044) retrieve doesn't retrive files if the current one is more recent

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene updated IVY-1044:
-------------------------------

    Issue Type: Improvement  (was: Bug)

> retrieve doesn't retrive files if the current one is more recent
> ----------------------------------------------------------------
>
>                 Key: IVY-1044
>                 URL: https://issues.apache.org/jira/browse/IVY-1044
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant, Core
>    Affects Versions: 2.0
>         Environment: Win XP, J2SE 1.6.0_11-b03
>            Reporter: Daniel Dekany
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> The "retrieve" task will not retrieve files (artifacts) whose file modification date is greater than of the file in the repository (in the "resolver"), not even if sync="true". This way the target directory goes out of sync if (a) the module is downgraded in the repository or (b) the developer has overwritten the artifact manually when experiencing with something. Thus the only way to keep the target directory in sync is deleting it before retrieving, but of course that means suboptimal performance, and makes sync="true" useless anyway. Simply, a file should be retrieved if the date (or size!) is *different* than in the repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (IVY-1044) retrieve doesn't retrive files if the current one is more recent

Posted by "Antoine Levy-Lambert (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865960#action_12865960 ] 

Antoine Levy-Lambert commented on IVY-1044:
-------------------------------------------

Thanks Maarten. I will try this. Antoine

> retrieve doesn't retrive files if the current one is more recent
> ----------------------------------------------------------------
>
>                 Key: IVY-1044
>                 URL: https://issues.apache.org/jira/browse/IVY-1044
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant, Core
>    Affects Versions: 2.0
>         Environment: Win XP, J2SE 1.6.0_11-b03
>            Reporter: Daniel Dekany
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> The "retrieve" task will not retrieve files (artifacts) whose file modification date is greater than of the file in the repository (in the "resolver"), not even if sync="true". This way the target directory goes out of sync if (a) the module is downgraded in the repository or (b) the developer has overwritten the artifact manually when experiencing with something. Thus the only way to keep the target directory in sync is deleting it before retrieving, but of course that means suboptimal performance, and makes sync="true" useless anyway. Simply, a file should be retrieved if the date (or size!) is *different* than in the repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (IVY-1044) retrieve doesn't retrive files if the current one is more recent

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene resolved IVY-1044.
--------------------------------

    Resolution: Fixed

I've added an 'overwriteMode' attribute to the ivy:retrieve task to configure when the destination files should be overwritten...

> retrieve doesn't retrive files if the current one is more recent
> ----------------------------------------------------------------
>
>                 Key: IVY-1044
>                 URL: https://issues.apache.org/jira/browse/IVY-1044
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant, Core
>    Affects Versions: 2.0
>         Environment: Win XP, J2SE 1.6.0_11-b03
>            Reporter: Daniel Dekany
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> The "retrieve" task will not retrieve files (artifacts) whose file modification date is greater than of the file in the repository (in the "resolver"), not even if sync="true". This way the target directory goes out of sync if (a) the module is downgraded in the repository or (b) the developer has overwritten the artifact manually when experiencing with something. Thus the only way to keep the target directory in sync is deleting it before retrieving, but of course that means suboptimal performance, and makes sync="true" useless anyway. Simply, a file should be retrieved if the date (or size!) is *different* than in the repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.