Kepler

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:

https://code.kepler-project.org/code/kepler/releases/test-releases//provenance/provenance.zip

instead of:

https://code.kepler-project.org/code/kepler/releases/test-releases/provenance-2.0.0/provenance-2.0.0.zip

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.