Import Dependent Modules for KAR doesn't work
If you create a KAR that depends on modules that you're not currently running, the KAR icon in the Components pane shows an exclamation mark and gives you the option to Import Dependent Modules. This action does not work however, because the modules it attempts to download don't exist -- the KAR MANIFEST.MF dependsOnModule and module-dependencies attributes are just storing module names without version numbers, so e.g. if you're configured to the test-releases area, and attempt to open a 'reporting KAR' in vanilla kepler, the import action will attempt to download:
An additional problem is that if this fails to download, you get an error message, but it's followed by a message saying 'Module Download Complete' as if it had worked.
Aaron and David - I'm not sure what your decision was on this - should a KAR created w/ particular modules always be openable by those modules, no matter their version? It seems like the KAR MANIFEST should store the exact versions of the modules that were used to create it, for future identification. Having already released 2.0, if changes to the KAR MANIFEST are made, they should be backward compatible to support KARs users may have already made.
#2 Updated by Derik Barseghian over 11 years ago
These changes will be put into a new 2.1 branch, and removed from the 2.0 branch.
Yesterday I made more progress on the current plan, which Matt explains here:
#3 Updated by Derik Barseghian over 11 years ago
As part of this I've removed the File=>Save and File=>Save As menu items. Since module-dependencies are stored in kar manifests, attempting to open a workflow as xml in a suite that doesn't support that workflow's needs would result in errors, and not the import module dependency prompt you now get for kars. Discussion for this menu change, and how to re-enable them is found here: