TaskNaming contains various helper methods for naming SWF tasks when submitted to SWF; so while the TaskNaming code isn't itself specific to SWF, it's implicitly written around SWF's naming requirements, and other backends do not necessarily have the same set of constraints.
The few references to TaskNaming in flux-common and flux-testutils will need to be removed/replaced with something else.
TaskNaming contains various helper methods for naming SWF tasks when submitted to SWF; so while the TaskNaming code isn't itself specific to SWF, it's implicitly written around SWF's naming requirements, and other backends do not necessarily have the same set of constraints.
The few references to TaskNaming in flux-common and flux-testutils will need to be removed/replaced with something else.