#2 is actually not an issue, you should just configure ivy to point to the Ivy.xml that comes out of the build, which will have absolute paths in it...
As far as the ivy 2 upgrade, I kinda feel like that should be a fork, since 2.0 isn't 100% backward compatable.
On Tue, Jun 24, 2008 at 9:49 AM, Simmendinger, Felix <[hidden email]> wrote:
Hello you both,
we are currently migrating our ci system
from cruise control to Hudson and since we are using ivy we would like to use
the ivy plugin to trigger our jobs. I've got two questions concerning the
1.When do you think will the
plugin support ivy 2.0.0 beta2 ???
2.It isn't possible to
parse ivy files where properties are used to define the location of a
configurations file to be included in the configurations element. Is there a
fix possible or should I wait to fix of point 1 above.
Here an example snippet of an ivy file that
cannot be parsed: