blank modules.txt files created for non-suite modules
Tomasz Zok reported a bug with invalid modules listed in the Module Manager Gui after patching a released module, and then kepler crashing after attempting to use a patched suite.
It's described here:
I commited Sean's fix for the bug to module-manager-gui at r28451.
We should issue a 2.2 module-manager-gui patch for this issue since people have already put work into making 2.2 add-ons.
#1 Updated by Derik Barseghian over 9 years ago
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.
#2 Updated by Derik Barseghian over 9 years ago
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.
#3 Updated by Derik Barseghian over 9 years ago
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:
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: