Kepler

I'm still seeing this problem with Sean's change at r28451.
To replicate edit your Kepler-2.2 app's module-manager configuration.xml to point at the test-releases area. Restart. Accept the patches. Kepler restarts. Open MM Gui, you'll see truncated modules names.

Ok, this problem can still manifest when a module's published zip file contains a blank modules.txt.

Some part of the build system can erroneously create blank module.txt files in non-suite modules.

Also note that when a published module's module-info/ directory contains a blank modules.txt file, this does not cause the bug, but does cause the (non-suite) module to show up as an Available Suite in the Module Manager GUI, which is not something you want.

The bug also occurs on the first startup of kepler after getting a patched suite that refers to other modules using carets. An example is first startup after receiving module-manager-gui-2.2.1. I don't know why.

Incidentally, I noticed that module-manager-gui-2.2.0's modules.txt refers to modules without using carets:
common-2.2.0
module-manager-2.2.0
configuration-manager-2.2.0
kepler-tasks-2.2.0
ptolemy-kepler-2.2.0

I don't know if this was accidental or intentional.This means that the standalone module manager gui will not utilize patches to these modules, unless it itself is patched to change its modules.txt to use carets. Since this seems bad, I've changed to using carets with module-manager-gui-2.2.1 and beyond:

common-2.2.^
module-manager-2.2.^
configuration-manager-2.2.^
kepler-tasks-2.2.^
ptolemy-kepler-2.2.^

I've issued the patch with module-manager-gui-2.2.1. at r28583.
The issues in comment 3 and 4 should still be fixed for 2.4.

Needs to be tested and evaluated at the end of release cycle.

The modules.txt files in Kepler 2.4 release candidates have correct carets and I didn't see empty modules.txt files for other modules. I also tried with suite and module patches and didn't see any problems. Closing the bug.

Original Bugzilla ID was 5487