In order to be able to test, debug and develop AMPs, we need to be able to deploy and run them in our nur Maven Development Environment.
The Module Management Tool in 5.1 contains a bug that prevents this.
This bug also affects the Alfresco SDK that is used by our customers to develop their own customizations.
Gethin James [X] is already working on a similar problem.
Since 5.1, the MMT is checking the version of Alfresco / Share by looking into the META-INF/MANIFEST.MF file.
The WarHelperImpl handles null values returned by findManifestAttribute properly. This is required to cope with missing properties in the manifest.
But if the manifest file itself is missing, it throws an Exception:
In our new Maven Development Environment, we run the Tomcat Maven Plugin on an exploded war. The META-INF/MANIFEST.MF file is created in the process of packing this exploded war into a .war file. Thus, this exploded war does not contain the manifest.
In findManifestArtibute, catch Exceptions log an info statement and return null.