Bug #3027
closedjar handling issues
0%
Description
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
Updated by Chad Berkley about 15 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.
Updated by Chad Berkley almost 15 years ago
Try to add shared jar files to one module instead of repeating them throughout the repository.
Updated by David Welker about 14 years ago
This older bug can be closed. Multiple versions of the same jar can now be handled through either overrides or a special option that allows you to run a module with it's own class loader.