Ant 1.5 Beta2 Released!

[Magesh Umasankar <um...@apache.org>]

This is to announce that Jakarta Ant-Dev has released
the second beta of the forthcoming 1.5 release of 
Apache Ant, a Java-based build tool.

The release is available in binary and source forms
at http://jakarta.apache.org/builds/jakarta-ant/release/v1.5Beta2/

If you notice any problems with this release, please notify 
Ant-Dev by filing a bug report at 
http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant

Ant-Dev plans to make the 1.5 final release on July 1, 2002.

Cheers,
Magesh

*************************************************************
*  Miser: A person who lives poor so that he can die rich.  *
*************************************************************


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

How to avoid "Trying to override old definition of task"

["Hal Hildebrand (web)" <Ha...@hellblazer.com>]

In 1.5 Beta 2, I still have the annoyingly prodigious output when I run
my builds:

Trying to override old definition of task <some task name>

Perhaps someone can show me how to accomplish the following without
generating these messages.

The build has a common include file which defines the tasks used
throughout the build.  The annoying message comes about when one task
calls another task in the build that exists in another project.  Since
they are including the same common XML include file, they are all
attempting to define the same task definitions.

This seems like a natural thing to do for even reasonably complex builds
and certainly seems in line with best practices.

So the question I have is how to do this without provoking the annoying
warning of Ant when this kind of pattern is used?

I can get rid of the messages by modifying line 822 of Project to:
                    MSG_VERBOSE);

It would seem that when this use of includes to define common tasks
throughout the build will inevitably trigger these messages because the
classes will always be different.

Is there something that I'm missing with respect to best practices
regarding of common task definitions in multiple projects of a build?

Thanks

-Hal
______
All your data-base are belong to us
www.hellblazer.com


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>