You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2007/06/25 20:39:26 UTC

[jira] Updated: (IVY-357) Update -Automatically invoke Any build scripts for dependencies

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

Maarten Coene updated IVY-357:
------------------------------

        Fix Version/s:     (was: 1.4-RC1)
    Affects Version/s: 1.4-RC1

Switched Affected/Fixed versions...

> Update -Automatically invoke Any build scripts for dependencies
> ---------------------------------------------------------------
>
>                 Key: IVY-357
>                 URL: https://issues.apache.org/jira/browse/IVY-357
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Ant
>    Affects Versions: 1.4-RC1
>            Reporter: Iain Coulter
>            Assignee: Xavier Hanin
>         Attachments: ZipUtil.java
>
>
> See this forum thread for more details: http://jayasoft.org/node/218
> The following is from one message in that thread:
> A resolver that wraps another resolver but also can invoke an ant build script for a dependency if an Ant script is available. The build script would be invoked at most once per build for each dependency. Something like this:
> 1. Need latest version for dependency "A".
> 2. Is there an Ant script for dependency "A"?
> - If yes: invoke script if it has not yet been invoked for this build
> 3. Call wrapped resolver to actually retrieve the published artifact(s).
> Note: I don't think this would apply if a specific version is being referenced - only if something like "test.integration" is being referenced?
> The trick then would be to figure out if a) a dependency has an Ant build script, b) where the script is located, and c) what target to call on the script.
> Then, all I do is tell Ivy to resolve in my main Ant build and it will do the rest to ensure that all my dependencies are up-to-date.

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