[
https://issues.apache.org/jira/browse/ARIES-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935126#comment-14935126
]
John Ross commented on ARIES-1423:
----------------------------------
Yes, that does leave you in a bit of a bind, doesn't it? Conceptually, I think
the issue is that we use the generic header for both unmapped OSGi headers as
well as unknown, non-OSGi headers. Perhaps we need some sort of a simple
passthrough mechanism for headers we don't care about.
> IllegalArgumentException when GenericHeader has no clauses
> ----------------------------------------------------------
>
> Key: ARIES-1423
> URL: https://issues.apache.org/jira/browse/ARIES-1423
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-2.0.3
> Reporter: Wouter Bancken
> Fix For: subsystem-2.0.3
>
> Attachments: MANIFEST.MF
>
>
> When trying to install a subsystem which contains bundles that have a
> manifest that contains empty headers, the AbstractClauseBasedHeader throws an
> IllegalArgumentException.
> Example headers are (manifest attached to this issue)
> {code}
> Build-Plan:
> Build-Number:
> {code}
> The exception is caused by the rework of the AbstractClauseBasedHeader for
> ARIES-1387.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
