Team,
I have some untraceable dependencies for one of my runnables. It occurs
to me that preparing and launching the runnable is not always the best
place to define these dependencies (using withDependences method). The
runnable itself will always have these deps (there is static xml
configuration embedded in the lib). What would folks think of the idea
of a tagging interface that TwillPreparer would check and insert the
deps itself.
Something like:
public interface HasDependencies {
Iterable<Class<?>> dependencies();
}
This interface could be added to any implementation of TwillRunnable.
Thoughts?
-Martin
