> in master.xml
>
>
>
>
>
>
>
>
>
master.xml
--
...
But that´s a lot of writing. And adding a new module is a lot of pain:
- you can generate these snippet
- you can use Gump
Jan
[EMAIL PROTECTED] wrote:
Provide a for each module and uses "depend"-attributes,
so Ant can handle the dependency managing of the "targets" (here
your modules) for you.
Let me describe my repository structure:
seda/
+---adisk/
| +---build.xml
|
+---asocket/
| +---build.xml
|
+---
[EMAIL PROTECTED] wrote:
Oh, another idea:
Provide a for each module and uses "depend"-attributes,
so Ant can handle the dependency managing of the "targets" (here
your modules) for you.
Thanks for your response. But, I am not an expert with Ant, so could
you explain your idea please.
Thanks,
J
> - the master buildfile doesnt use , it uses a
> sequence of
> calls
> where you manage (by brain :) the dependencies.
Oh, another idea:
Provide a for each module and uses "depend"-attributes,
so Ant can handle the dependency managing of the "targets" (here
your modules) for you.
Jan
Thanks, it's exactly the kind of information that I'm searching. But
it seems that these modules are independent. Where module dependencies
should be specified?
[EMAIL PROTECTED] wrote:
The Jakarta Commons project has also a set of independent modules [1].
They have a buildfile for each modul
of
calls
where you manage (by brain :) the dependencies.
Jan
> -Ursprüngliche Nachricht-
> Von: Jean Morissette [mailto:[EMAIL PROTECTED]
> Gesendet am: Montag, 13. Dezember 2004 08:50
> An: Ant Users List
> Betreff: Re: AW: Write Ant files for many modules
>
>
The Jakarta Commons project has also a set of independent modules [1].
They have a buildfile for each module. Each module has its own build path.
And their master buildfile [2] calls several modules.
Mmmh - there was a discussion when and were new ...
Yep: [3]. And I knew that some of us had don
