incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-340) Ability to have multiple roots in the <ivy:buildfilelist> task
Date Sat, 06 Jan 2007 11:53:27 GMT

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

Xavier Hanin resolved IVY-340.
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

I've integrated your patch, it seems to work pretty well. And thanks for the doc patch, it
wasn't easy to write one with the old raw-book format, should be easier in the future with
the new format (in the doc directory).

Thanks a lot for your contribution!

> Ability to have multiple roots in the <ivy:buildfilelist> task
> --------------------------------------------------------------
>
>                 Key: IVY-340
>                 URL: https://issues.apache.org/jira/browse/IVY-340
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>    Affects Versions: 1.4
>            Reporter: Matt Inger
>         Assigned To: Xavier Hanin
>             Fix For: 1.5
>
>         Attachments: buildlist_multipleroots.diff
>
>
> It would be extremely beneficial to have the ability to supply multiple roots in the
<ivy:buildfilelist> task.
> Support for instance, you have 10 applications in the same source tree, but only certain
apps change
> over a given development cycle.  It would be nice to be able to build only that set of
apps and their
> dependencies during the automated build. (Our build takes a property, and creates the
buildfilelist
> accordingly based on whether the property is set or not).
> Right now, only 1 root can be specified:
> <ivy:buildfilelist root="app1" ... />
> i propose a comma seperated list (or any reasonable delimiter) to specify multiple roots:
> <ivy:buildfilelist root="app1,app2" ... />

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message