[
https://issues.apache.org/jira/browse/KARAF-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801434#comment-16801434
]
ASF subversion and git services commented on KARAF-6207:
--------------------------------------------------------
Commit f40bf2475ebb8142494c2e86770a12408ec5b9d6 in karaf's branch
refs/heads/karaf-4.2.x from Lars Kiesow
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=f40bf24 ]
KARAF-6207, bootFeatures sometimes being ignored
According to the documentation, the maven-karaf-plugin will install
features listed in the installedFeatures in the "system" internal
repository. Features listed in bootFeatures are additionally added to
the boot-features in the features service configuration file.
Hence, the configuration options do not conflict and a configuration
like this should result in the features being installed and added to the
boot-features configuration:
<configuration>
<bootFeatures>
<feature>foo</feature>
</bootFeatures>
<installedFeatures>
<feature>foo</feature>
</installedFeatures>
</configuration>
In fact, the configuration should be equivalent to `foo` being listed
just as a bootFeature.
But what actually happens is that the installedFeature will overwrite
the bootFeature and the feature is not added to the boot-features
configuration.
This patch switches the handling of bootFeatures and installedFeatures
which makes a feature configured in both sections a bootFeature,
adhering to the specifications of both configurations.
> bootFeatures sometimes being ignored
> ------------------------------------
>
> Key: KARAF-6207
> URL: https://issues.apache.org/jira/browse/KARAF-6207
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.2
> Reporter: Lars Kiesow
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Labels: tooling
>
> According to the documentation, the maven-karaf-plugin will install features
> listed in the installedFeatures in the "system" internal repository. Features
> listed in bootFeatures are additionally added to the boot-features in the
> features service configuration file.
> Hence, the configuration options do not conflict and a configuration like
> this should result in the features being installed and added to the
> boot-features configuration:
>
> {code:java}
> <configuration>
> <bootFeatures>
> <feature>foo</feature>
> </bootFeatures>
> <installedFeatures>
> <feature>foo</feature>
> </installedFeatures>
> </configuration>{code}
>
>
> In fact, the configuration should be equivalent to _foo_ being listed just as
> a bootFeature.
> But what actually happens is that the installedFeature will overwrite the
> bootFeature and the feature is not added to the boot-features configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
