You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Erik Hatcher <ja...@ehatchersolutions.com> on 2001/12/03 14:22:06 UTC
Task.setTaskType
Is this method intentionally package-scoped rather than public? Just
curious.
What is it used for other than in output messages?
And shouldn't taskName be used instead in messages?
Thanks,
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Task.setTaskType
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 3 Dec 2001, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> Is this method intentionally package-scoped rather than public?
intentionally. task-type is what it has been called in the build file
as an element, task-name is the same, unless the user has specified
the taskname attribute, which ovverides the value.
> What is it used for other than in output messages?
It isn't used for output messages, task-name is. At least in
DefautlBuildLogger.
It is used to identify which incarnation of a class has been asked
for, the only current use of which is to print deprecation warnings
(if you use ecpand to run unzip or javadoc2 to run javadoc).
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>