[
https://issues.apache.org/jira/browse/KARAF-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168873#comment-16168873
]
Jérémie Brébec commented on KARAF-5372:
---------------------------------------
In order to fix KARAF-5371, I have patched the feature jar with a custom
version (4.1.2.a), and I wanted to install this version instead of the 4.1.2. I
do the same for bugs in pax-web or others librairies. however, it's not simple
to make a distribution with a patch for the feature.jar
The startup.properties is generated by the karaf-maven-plugin, and I don't want
to add a patched startup.properties in git for all of my containers, and ask
for all the teams to do the same for their own application (I manage a lot of
applications based on Karaf, and some of them are built by other teams - I
don't want those teams to have to fix this kind of low level bugs, they just
use a profile and a kar for now)
> 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)
