Exporting an actor to a kar does not include internal jars
It is now possible to include jars with class files needed by an actor inside a kar file. One can add these kars to the kar/actors/ directory or load them from the File/Import Archive menu. Note that these kar files are currently created by 'hand' and are of use in inserting new actors without rebuilding all of Kepler.
However, if one tries to create a kar from an actor in the work area, the jar information is lost! That seems to be because the kar is built only from the moml of the display which does not know that a kar for the actor already exists! (I think the same problem occurs when Uploading to the Registry.)
The menu action to create a kar should check to see if a kar already exists and modify it as necessary. Or an additional dialog should appear that allow the user to add various resources to the created kar.
#1 Updated by Chad Berkley over 12 years ago
When you export an actor to a kar file, it now asks you if you want to include the class file. if so, any associated class files are put in a jar and added to the kar file. By associated class files, I only mean the normal class files that go with that particular Class. For instance, if your actor is XYZ.class, there might be XYZ.class, XYZ$1.class, XYZ$someinnerclass.class, etc. All of them are found and included in the jar. Dependencies, however are still not included. Currently there is insufficient metadata on dependencies to complete this task.