You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Felix Simmendinger (JIRA)" <ji...@apache.org> on 2008/05/30 10:19:46 UTC

[jira] Created: (IVY-824) antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)

antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: IVY-824
                 URL: https://issues.apache.org/jira/browse/IVY-824
             Project: Ivy
          Issue Type: Bug
          Components: Ant
    Affects Versions: 2.0.0-beta-2
         Environment: vista 32 bit java 1.5.
Multimodule project where only some of the modules are checked out from vcs. Not checked out dependencies are resolved from a shared repository. Build modules are published to a local repository.
            Reporter: Felix Simmendinger


When there is an execution order where your publish task is executed after an antcall is made to a target where a nested retrieve is done, the publish task will use {{latest.integration}}  in the published ivy.xml instead of the previously published revision found in the local repository.

If you change antcall and add the target to the depends-list everything works like expected and the revision replaced in the published ivy.xml will be correct.


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

[jira] Resolved: (IVY-824) antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)

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

Maarten Coene resolved IVY-824.
-------------------------------

       Resolution: Invalid
    Fix Version/s:     (was: 2.0.0-beta-2)

> antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-824
>                 URL: https://issues.apache.org/jira/browse/IVY-824
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-beta-2
>         Environment: vista 32 bit java 1.5.
> Multimodule project where only some of the modules are checked out from vcs. Not checked out dependencies are resolved from a shared repository. Build modules are published to a local repository.
>            Reporter: Felix Simmendinger
>
> When there is an execution order where your publish task is executed after an antcall is made to a target where a nested retrieve is done, the publish task will use {{latest.integration}}  in the published ivy.xml instead of the previously published revision found in the local repository.
> If you change antcall and add the target to the depends-list everything works like expected and the revision replaced in the published ivy.xml will be correct.

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

[jira] Closed: (IVY-824) antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)

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

Felix Simmendinger closed IVY-824.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-2

its not a bug it was just a misconfiguration of our settingsfile, where the ivypattern matched to our workspace version and not a delivered one.

> antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-824
>                 URL: https://issues.apache.org/jira/browse/IVY-824
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-beta-2
>         Environment: vista 32 bit java 1.5.
> Multimodule project where only some of the modules are checked out from vcs. Not checked out dependencies are resolved from a shared repository. Build modules are published to a local repository.
>            Reporter: Felix Simmendinger
>             Fix For: 2.0.0-beta-2
>
>
> When there is an execution order where your publish task is executed after an antcall is made to a target where a nested retrieve is done, the publish task will use {{latest.integration}}  in the published ivy.xml instead of the previously published revision found in the local repository.
> If you change antcall and add the target to the depends-list everything works like expected and the revision replaced in the published ivy.xml will be correct.

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

[jira] Reopened: (IVY-824) antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)

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

Maarten Coene reopened IVY-824:
-------------------------------


> antcall to a target with a nested retrieve followed by a publish leads to a wrong revision attribute in the published ivy.xml (lates.integration instead of correct revision)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-824
>                 URL: https://issues.apache.org/jira/browse/IVY-824
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-beta-2
>         Environment: vista 32 bit java 1.5.
> Multimodule project where only some of the modules are checked out from vcs. Not checked out dependencies are resolved from a shared repository. Build modules are published to a local repository.
>            Reporter: Felix Simmendinger
>             Fix For: 2.0.0-beta-2
>
>
> When there is an execution order where your publish task is executed after an antcall is made to a target where a nested retrieve is done, the publish task will use {{latest.integration}}  in the published ivy.xml instead of the previously published revision found in the local repository.
> If you change antcall and add the target to the depends-list everything works like expected and the revision replaced in the published ivy.xml will be correct.

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