Project

General

Profile

Bug #3027

jar handling issues

Added by Dan Higgins almost 12 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
general
Target version:
Start date:
12/13/2007
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3027

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

History

#1 Updated by Chad Berkley over 10 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.

#2 Updated by Chad Berkley over 10 years ago

Try to add shared jar files to one module instead of repeating them throughout the repository.

#3 Updated by David Welker over 9 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.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 3027

Also available in: Atom PDF