Community
Participate
Working Groups
Build R2.1 If multiple tools are producing tasks, then it will become likely an issue to figure which tool did produce the offending task. Unless tasks are carrying this information, it will be quite difficult.
I suggest to extend the idea of keeping the 'task producing tool' to keeping the 'task producing resource' which may be a user. This should be combined with team support. Furthermore a time/date creation field per task is desirable.
*** Bug 103847 has been marked as a duplicate of this bug. ***
Since 103847 is marked as a duplicate I assume you are planning to add this as an attribute of markers in general? Any update on the status of this? This is a request we need to push on as it is causing a usability issue since currently these id's are typically added as a prefix to the marker's message
Sorry Randy, I lost track of this bug. I'll add the attribute key this week (3.3 stream).
Created attachment 50826 [details] Preview of new attribute key and javadoc
Fix released. New attribute added.
Randy: I should mention that although the attribute key only appears as API in Eclipse 3.3, there is nothing stopping you from beginning to use this attribute against prior releases of the platform.
Thanks. I'd like to request this be added to the 3.2 maintenance stream as well. We will not be moving to the 3.2 stream until after the next maintenance release. The reason we need it added to the base marker and not just add it ourselves is that we can then ask platform UI to add it as a column in the Problems view and/or Problem property dialog.
As a rule we don't add new API in maintenance streams. However, in this case it's not needed. The only thing added in core was a String constant that tells you the attribute key is "generatedBy". If necessary your tools, or the problems view, could start using that attribute in 3.2.x without the constant being there (based on the knowledge that the API has already been added in the 3.3 stream and that the key won't change).
