[jboss-jira] [JBoss JIRA] (WFLY-1090) Allow Dependencies: header to be empty, don't throw exception or fail deployment startup

[Stuart Douglas (JIRA)]

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

Stuart Douglas resolved WFLY-1090.
----------------------------------

    Resolution: Duplicate Issue


Duplicates WFLY-232
                
> Allow Dependencies: header to be empty, don't throw exception or fail deployment startup
> ----------------------------------------------------------------------------------------
>
>                 Key: WFLY-1090
>                 URL: https://issues.jboss.org/browse/WFLY-1090
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Class Loading
>         Environment: EAP6.1
>            Reporter: Darryl Miles
>            Assignee: David Lloyd
>
> Exception throw for empty "Dependencies:" header in MANIFEST.MF.
> This is a perfectly well-formed header and should have the same meaning as if the header does not exist.
> By all means emit a warning explaining which JAR the MANIFEST.MF is in, the header name and that the value is an empty string and this is not allow (due to some spec/rule you cite).
> But don't fail a deployment from starting.
> Sometimes headers are not going to be perfect from dependent JARs you have little control over.  You don't want to make the user do extra work of repacking/fixing those JAR just to get them to deploy on JBoss AS.
> If the empty header has a special meaning then I suggest you use a keyword token instead.  Like you do for "export", "services" and "optional".

--
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