ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Kiesel <>
Subject Bundle build scripts
Date Tue, 22 Feb 2011 07:32:18 GMT

after having fiddled around with maven for too long, I have tried
ivy+ant and things look promising, so far. I like some of the concepts
of maven, though, like convention over configuration for example, or
the idea of being able to publish a pom.xml as an artifact.

After having built quite some targets to be able to properly build and
package my software, I would like to benefit from that infrastructure
in other projects (actually, even projects that somehow interact /
depend / connect to). I don't want to introduce implicit dependencies
onto different svn trees or onto different directories in the same
source checkout (because they ought to be independent from each
other). This is where the maven pom packaging comes into play and for
what I have not yet found a nice ivy alternative (I see that this also
is not primary focus for ivy).

Did anyone ever package his / her build scripts in a separate artifact
and distribute them this way? Theoretically, this would easily be
possible - an issue is, however, how to load these dependencies before
the actual build system has been fetched.

Thanks for your hints!


View raw message