Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353964 - TaskAttribute should not permit null values
Summary: TaskAttribute should not permit null values
Status: CLOSED MOVED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2011-08-05 02:28 EDT by Sam Davis CLA
Modified: 2011-08-11 06:55 EDT (History)
1 user (show)

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 Sam Davis CLA 2011-08-05 02:28:16 EDT 
The setValue method of TaskAttribute checks that its argument is not null, but the setValues method does not check that each element of its list argument is not null, so clients cannot rely on the value(s) not being null.
Comment 1 Steffen Pingel CLA 2011-08-11 06:55:09 EDT 
Agreed. We should add checks and test cases to verify that none of the values are null.
Comment 2 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST 
Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn