Issue Feature Closed

#25652Example AdditionalFieldsProvider

Nils Blattner 02/23/10, 13:43 updated 12/10/13, 01:27

Description

Last weekend I showed my AdditionalFieldsProvider to Christian Kuhn and he told me to post it here so it might be included in a future release as an example class.
Should it be desired, I would “pimp” it a bit more to make it general enough so it could be included as a library class (or the like).
The class already does create a kind of namespace between different tasks (provided it is extended for each such task class). However, I could change the class to also to provide namespacing between different tasks of the same type.
The question there is whether you want to fix these problems in the scheduler itself or not.

Anyway, let me know what you decide :)

(issue imported from #M13628)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.