Project

General

Profile

Actions
Copy link

Bug #4317

closed

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

Added by Aaron Aaron over 15 years ago. Updated almost 15 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Aaron Aaron
Category:
core
Target version:
2.X.Y
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 filesResolvedAaron Aaron10/27/2004

Actions
Blocks Kepler - Bug #4340: Resolve KAR file/module formatResolvedAaron Aaron08/26/2009

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

Actions
Actions
Copy link
 #1

Updated by Chad Berkley almost 15 years ago

this can be pushed to post 2.0

Actions
Copy link
 #2

Updated by Aaron Aaron almost 15 years ago

A KAR's module dependencies are now included in the KAR manifest file and are accessible through the KARFile class.

Actions
Copy link
 #3

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 4317

Actions
Copy link

Also available in: Atom PDF