[
https://issues.apache.org/jira/browse/FELIX-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521831
]
Stuart McCulloch commented on FELIX-343:
----------------------------------------
yes, I agree - it looks much clearer with the option inside Include-Resource.
perhaps:
<Include-Resource>${maven-resources},my/resources</Include-Resource>
would be even clearer, as it shows it's related to maven resource paths?
it is a band-aid, but a useful one as otherwise it's harder to move certain
maven projects over to the bundle process (at least in a standard way...)
> Add "additional-Resource" option
> --------------------------------
>
> Key: FELIX-343
> URL: https://issues.apache.org/jira/browse/FELIX-343
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: 1.0.0
> Reporter: Carsten Ziegeler
> Attachments: patch.txt
>
>
> The "Include-Resource" option is currently a all-or-nothing option which is
> directly forwarded to bnd. One can either use the default (the maven resource
> paths) or specify the whole paths oneself. In many cases it is more desirable
> to just provide additional paths to the default maven paths.
> Therefore I created a patch which adds an "addtional-Resource" property. The
> logic is as follows:
> - If Include-Resource is specified but no additional-Resource:
> Include-Resource is forwarded to bnd
> - If Include-Resource is specified and additional-Resource:
> Include-Resource+','+additionalResource is forwarded to bnd
> - if no Include-Resource is specified and no additional-Resource: maven
> resource paths are forwarded to bnd
> - if no Include-Resource is specified and additional-Resource is given: maven
> resource paths + additionalResource are forwarded to bnd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
