> I think it's just a different design.
> In mine the "common" build file already contains everything I
> need for a
> typical project out of the box.
> The purpose of the including build file is just to add/rewrite/extend
> custom stuff. For very basic projects it just adds a target
> to pack
Maybe that´s historical: when writing that peace of code I tested the
paths _inside_ the buildfile and then extracting that into common.xml :)
Jan
> -Ursprüngliche Nachricht-
> Von: Dominique Devienne [mailto:[EMAIL PROTECTED]
> Gesendet am: Mittwoch, 6. Oktober 2004 16:46
> An: Ant User
This will cause the annoying
Overriding previous definition of reference to classpath.additional
message.
There is a bug report requesting the reduction of this message to verbose,
perhaps this would be a good thing to do!
Peter
[EMAIL PROTECTED] wrote:
yep:
common.xml:
---
yep:
common.xml:
---
build.xml:
--
Other than properties paths will be muted. Therefore the build.xml imports
the additional
classpath and overrides it after it (with properties you have to import
after prop-settings).
The
