jar handling issues
We still need to treat all 'legacy' actor jars - i.e. figure out which jars go
with which actors and are any shared. And figure out how to handle jar version issues.
This bug is derived from #2316 - now closed
#1 Updated by Chad Berkley almost 11 years ago
This should be handled through modularization of kepler. The jars that go with an actor should reside with it in its module. Many actors are currently stored together all in one module with their classes and jars spread across other modules. This should be fixed by reorganizing the modules.