Bug #4317
KAR's dependencies on modules need to be included in KAR metadata
Start date:
08/14/2009
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
4317
Description
When starting Kepler with a kar in a local repository that needs a module that is not in the current suite, a ClassNotFound error is thrown. Need to properly handle this error by including module dependency information within KAR files and checking that dependency information before trying to open the KAR file.
Related issues
History
#1 Updated by Chad Berkley over 12 years ago
this can be pushed to post 2.0
#2 Updated by Aaron Aaron over 12 years ago
A KAR's module dependencies are now included in the KAR manifest file and are accessible through the KARFile class.
#3 Updated by Redmine Admin about 9 years ago
Original Bugzilla ID was 4317