[
https://issues.apache.org/jira/browse/KARAF-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187711#comment-16187711
]
Guillaume Nodet commented on KARAF-5372:
----------------------------------------
What you can do is provide your own kar file as a framework instead of using
the default karaf one.
Or you can use the default kar file, but provide a different framework feature
to install for startup.
The {{startup.properties}} file is generated by the maven plugin, mainly from
the startup features, so you have control over it if you point to your own
feature instead of the default {{framework}} feature from Karaf.
> startup.properties doesn't respect overrides
> --------------------------------------------
>
> Key: KARAF-5372
> URL: https://issues.apache.org/jira/browse/KARAF-5372
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 4.1.2
> Reporter: J. Brébec
> Assignee: Guillaume Nodet
>
> The karaf-maven-plugin doesn't take into account bundles overrides. The karaf
> main doesn't use it either. As a consequence, it is not possible to override
> core bundle as fileinstall or features-core
> For a real usecase, I was trying to patch locally KARAF-5371 (which is a
> blocker issue in my context), but it's not possible to override the
> feature-core bundle. I have to overwrite the jar with a patched version after
> the assembly goal..
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
