Bug 27500 - Ant tasks do not always have a name
Summary: Ant tasks do not always have a name
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 2.1 M4   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2002-12-02 10:56 EST by Darin Swanson CLA
Modified: 2002-12-02 11:24 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Swanson CLA 2002-12-02 10:56:55 EST 
It is possible for an Ant task to not have an associated name.
For example if a user creates a custom task that makes use of another supplied 
task (like Echo), the task name may not be set and everything else can work 
normally.
This gives a NPE in AntProcessBuildLogger#getAdornedMessage(BuildEvent, 
StringBuffer).

Ant from the command line reports the null...eg [null]
Comment 1 Darin Swanson CLA 2002-12-02 10:57:40 EST 
I have mimiced the cmd line behavior.
Please verify.
Comment 2 Darin Wright CLA 2002-12-02 11:24:59 EST 
Verified