karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5372) startup.properties doesn't respect overrides
Date Fri, 15 Sep 2017 11:08:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167713#comment-16167713
] 

Guillaume Nodet commented on KARAF-5372:
----------------------------------------

That's definitely not possible.  The override mechanism is handled by the FeaturesService
and during startup, the requirements can't be met.
What do you mean by "patching" exactly ? Because startup bundles are only installed the first
time, so if you want, you could just modify the etc/startup.properties directly before the
first start of the container.

> 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
>
> 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)

Mime
View raw message