Deployment fails when Dependencies is empty in a jars manifest -------------------------------------------------------------- Key: WFLY-232 URL: https://issues.jboss.org/browse/WFLY-232 Project: WildFly Issue Type: Enhancement Reporter: Gábor Farkas Assignee: Stuart Douglas Fix For: 8.0.0.Alpha1 Attachments: empty-manifest.ear I have a WAR, which produces the following error on deployment: Caused by: java.lang.IllegalArgumentException: Empty module specification at org.jboss.modules.ModuleIdentifier.fromString(ModuleIdentifier.java:169) [jboss-modules.jar:1.1.1.GA] at org.jboss.as.server.deployment.module.ManifestDependencyProcessor.deploy(ManifestDependencyProcessor.java:83) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more I found that my WAR contains a jar in WEB-INF/lib that has empty dependencies defined in its manifest. More exactly it's "Dependencies: ", so the colon is followed by a space character before the new line characters. The ManifestDependencyProcessor parses this as one dependency, the name of which is the empty string.