Mitch, Maarten,
These are indeed interesting ideas. For what I want to do now, I think the
best choice will be what Mitch suggested by creating build-configurations in
an ivy.xml file.
The reason why I prefer not to resolve inline, is that I would like to
separate the build-logic from the version
- <-- email is about this
+ <-- email is about this
Jan
>-Ursprüngliche Nachricht-
>Von: Robert Menteer [mailto:reet...@me.com]
>Gesendet: Mittwoch, 10. März 2010 21:28
>An: user@ant.apache.org
>Betreff: Passing a list of files to javac
>
>How can I get the javac task
Marc, doing everything at once at init sounds a bit heavyweight and
monolithic. Imagine you're resolving and retrieving 15 different task
libraries when all you need for a given build is two or three.
Instead, I would obtain tasks on an as-needed basis. So for example, the
moment you need a partic
Hi Mitch,
Thanks for your suggestion. I'll try to do the following:
In my central build file (used for building all projects), I will create an
init-target which will:
* execute an ivy:init
* do an ivy:retrieve using that common ivy.xml file for the dependencies of
my build-system itself. The app
How can I get the javac task to use an existing fileset? In my build.xml I have
created several filesets to be used in multiple places throughout build file.
Here is how they have been defined:
I have also used
I realize that the problem is because I try to use an AC variable in a
fileset include attribute like in the following example
