Project

General

Profile

Bug #4317

KAR's dependencies on modules need to be included in KAR metadata

Added by Aaron Aaron about 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
core
Target version:
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

Blocked by Kepler - Bug #1750: Allow KAR files to include jar/class filesResolved10/27/2004

Blocks Kepler - Bug #4340: Resolve KAR file/module formatResolved08/26/2009

Blocks Kepler - Bug #4516: Module Manager needs ability to install modules needed by KARsResolved10/29/2009

History

#1 Updated by Chad Berkley over 9 years ago

this can be pushed to post 2.0

#2 Updated by Aaron Aaron over 9 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 over 6 years ago

Original Bugzilla ID was 4317

Also available in: Atom PDF