[jboss-jira] [JBoss JIRA] (AS7-5547) Deployment fails when Dependencies is empty in a jars manifest

[Gábor Farkas (JIRA)]

     [ https://issues.jboss.org/browse/AS7-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gábor Farkas updated AS7-5547:
------------------------------

    Affects Version/s: 7.1.1.Final
                           (was: 7.1.2.Final (EAP))

    
> Deployment fails when Dependencies is empty in a jars manifest
> --------------------------------------------------------------
>
>                 Key: AS7-5547
>                 URL: https://issues.jboss.org/browse/AS7-5547
>             Project: Application Server 7
>          Issue Type: Enhancement
>    Affects Versions: 7.1.1.Final
>            Reporter: Gábor Farkas
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira