Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338347 - Options in TaskAttribute are not used
Summary: Options in TaskAttribute are not used
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-27 13:38 EST by Frank Becker CLA
Modified: 2011-09-28 08:56 EDT (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 Frank Becker CLA 2011-02-27 13:38:00 EST 
Actual the options in TaskAttribute are not used. Instead BugzillaAttributeMapper.getOptions use the options from the RepositoryConfiguration.

I think we should 
a) remove  set of the options in the TaskAttributes (RepositoryConfiguration.updateAttributeOptions)
b) BugzillaAttributeMapper.getOptions must detect if the RepositoryConfiguration has changed since update of the TaskAttribute Options.

I think we should implement b) and use the lastModifiedHeader field and store it in the root TaskAttribute.

Thoughts?
Comment 1 Steffen Pingel CLA 2011-02-27 18:25:27 EST 
The options are saved in the attribute in case the configuration is lost, e.g. due to an update of the schema. We should consider an API to inform the framework when the configuration changes or update it in place when a change is detected.

I'm -1 on the proposed changes. I believe the current implementation is sufficient for providing the latest options, e.g. for display in the task editor.
Comment 2 Steffen Pingel CLA 2011-09-28 08:56:47 EDT 
I'm marking this wontfix as per comment 1. Please feel free to reopen if I am missing anything.