ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38458] - [PATCH] NullPointerException thrown in Task.log() if setProject() has not been called
Date Thu, 02 Feb 2006 08:50:08 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38458>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38458





------- Additional Comments From peterreilly@apache.org  2006-02-02 09:50 -------
I am afraid not, This would cause so many Backword and Forward compatibly
problems, it would not be funny.

All most ant objects live in a Project context. A Project context provides a large
number of servies - properties, location of build file, references, tasks/type etc.
Just creating a project in a ant object constructor is not sufficient.

One way to look at project would be as a kind of ejb container.

Perhaps every task should enforce the need to have the project
in the constructor. However ant objects normally do not enforce having
the construtor make a valid object. Doing this would make
xml -> java reflection configured objects impossible.

In any case, ant code changes are *very* conservative. Normally
a public method or constructor is not allowed to be removed or changed
in new releases of ant.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message