Project

General

Profile

Bug #4340

Resolve KAR file/module format

Added by Chad Berkley almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
core
Target version:
Start date:
08/26/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4340

Description

We need to resolve the differences between the KAR file format and the module format because we have two different ways of storing very similar information. This relates to bugs 1750 and 4317. It would be nice if a kar file could include all of the same information as a module so that modules can be transported in similar ways as kars. The kar import/export system needs to know how to process actors and workflows as well as the jars/classes that they depend on.


Related issues

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

Blocked by Kepler - Bug #4317: KAR's dependencies on modules need to be included in KAR metadataResolved08/14/2009

Blocked by Kepler - Bug #4316: re-evaluate how kars are managed in the build and runtimeResolved08/14/2009

History

#1 Updated by Chad Berkley over 9 years ago

We have now done this, as far as the 2.0 release is concerned. the KAR and module format will remain separate with kars depending on modules as needed.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4340

Also available in: Atom PDF