You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Ross Camara (JIRA)" <ji...@apache.org> on 2008/08/06 22:34:44 UTC

[jira] Created: (IVY-875) post-download-artifact trigger

post-download-artifact trigger
------------------------------

                 Key: IVY-875
                 URL: https://issues.apache.org/jira/browse/IVY-875
             Project: Ivy
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0.0-beta-2, 2.0
            Reporter: Ross Camara


The file property provided by the post-download-artifact trigger points to a file within the cache and not to the actually file in specified retrieve location. 

The description of the the trigger does not indicate if the file should already be in place however I believe this is a reasonable expectation. This would allow users of this trigger perform actions on the downloaded artifact. 

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


[jira] Resolved: (IVY-875) post-download-artifact trigger file.property points to cache location

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

Xavier Hanin resolved IVY-875.
------------------------------

    Resolution: Invalid

This is actually the expected behaviour. Indeed files are downloaded to Ivy cache before being copied at retrieve time. This is explained in "how it works" page of the documentation, and since retrieve is not mandatory, I don't see how post-download-artifact file attribute could point to sg different.

Now you may want to open an issue to ask for a new event triggered after an artifact is retrieved. In this case the file location would obviously be the retrieved location.

> post-download-artifact trigger file.property points to cache location
> ---------------------------------------------------------------------
>
>                 Key: IVY-875
>                 URL: https://issues.apache.org/jira/browse/IVY-875
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-beta-2, 2.0
>            Reporter: Ross Camara
>
> The file property provided by the post-download-artifact trigger points to a file within the cache and not to the actually file in specified retrieve location. 
> The description of the the trigger does not indicate if the file should already be in place however I believe this is a reasonable expectation. This would allow users of this trigger perform actions on the downloaded artifact. 

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


[jira] Updated: (IVY-875) post-download-artifact trigger file.property points to cache location

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

Ross Camara updated IVY-875:
----------------------------

    Summary: post-download-artifact trigger file.property points to cache location  (was: post-download-artifact trigger)

> post-download-artifact trigger file.property points to cache location
> ---------------------------------------------------------------------
>
>                 Key: IVY-875
>                 URL: https://issues.apache.org/jira/browse/IVY-875
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-beta-2, 2.0
>            Reporter: Ross Camara
>
> The file property provided by the post-download-artifact trigger points to a file within the cache and not to the actually file in specified retrieve location. 
> The description of the the trigger does not indicate if the file should already be in place however I believe this is a reasonable expectation. This would allow users of this trigger perform actions on the downloaded artifact. 

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