Creating a server/runtime out of a patch-build wildfly8.1.0.CR4 cannot correctly determine the version of the given home directory.

The reason for this bug is that the class in charge of discovering a server version is looking for a jar that can properly give the versioning information. For wildfly, we are looking to introspect the jar modules/system/layers/org/jboss/as/server/main/*.jar. And we are looking for the manifest.mf property key: JBossAS-Release-Version

Currently, trying to introspect this jar fails, because the jar is an invalid jar file.

It must be recognized that there is now no safe way / agreed-upon API to determine the version of a given server installation when the server is stopped.

There are options:
1) We respect the module structure / overlay layout and simply look for the correct module folder for "org.jboss.as.server", or
2) We agree to one single file that will be updated and hold the version information for a given project or product release.