--- Johan Vromans CPWR
<[EMAIL PROTECTED]> wrote:
> I'm currently experimenting with an enhanced version
> of the import task.
> I've added a boolean attribute "float" that, when
> enabled, will have the import
> float upwards the root of the file system to find
> the file to be imported.
> I've d
--- Matt Benson <[EMAIL PROTECTED]> wrote:
> Actually, $HOME/.antrc, $HOME/.ant/ant.conf, and
> /etc/ant.conf are all detected and sourced by the
> ant
> shell script, and they can do a lot for you, but all
> they can really do is set properties. This is good,
> but a facility to execute buildfile
--- "Jack J. Woehr" <[EMAIL PROTECTED]> wrote:
> Matt Benson wrote:
>
> > I tend to agree that having a means of doing with
> > actual Ant buildfiles what we basically do using
> > environment variables such as ANT_OPTS and
> ANT_ARGS
> > might be nice for advanced users, if a little
> > dangerous
--- Johan Vromans CPWR
<[EMAIL PROTECTED]> wrote:
[SNIP]
> We want to avoid wrapper scripts (for ant) since we
> have multiple platforms to
> maintain. For that reason we would like to do it
> with ant only. A pre-import
> would make that possible.
I tend to agree that having a means of doing wi
Matt Benson wrote:
> I tend to agree that having a means of doing with
> actual Ant buildfiles what we basically do using
> environment variables such as ANT_OPTS and ANT_ARGS
> might be nice for advanced users, if a little
> dangerous for widespread use in environments with less
> than optimal co
