[jboss-jira] [JBoss JIRA] (AS7-6975) Allow Dependencies: header to be empty, don't throw exception or fail deployment startup
David Lloyd (JIRA)
jira-events at lists.jboss.org
Tue Apr 23 10:20:53 EDT 2013
[ https://issues.jboss.org/browse/AS7-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Lloyd moved MODULES-164 to AS7-6975:
------------------------------------------
Project: Application Server 7 (was: JBoss Modules)
Key: AS7-6975 (was: MODULES-164)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: 1.2.0.CR1)
Component/s: Class Loading
(was: core)
> Allow Dependencies: header to be empty, don't throw exception or fail deployment startup
> ----------------------------------------------------------------------------------------
>
> Key: AS7-6975
> URL: https://issues.jboss.org/browse/AS7-6975
> Project: Application Server 7
> 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
More information about the jboss-jira
mailing list