You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Vadim Belov (JIRA)" <ji...@apache.org> on 2019/07/24 17:39:00 UTC
[jira] [Commented] (KARAF-5678) Existing configfiles (in kar) may
be overwritten when building assembly
[ https://issues.apache.org/jira/browse/KARAF-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892035#comment-16892035 ]
Vadim Belov commented on KARAF-5678:
------------------------------------
https://issues.apache.org/jira/browse/KARAF-5678?focusedCommentId=16415272&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16415272
I would agree with [~jbonofre] - there should be an option to override default config files explicitly. Otherwise it's not clear for what purpose we have _org.ops4j.pax.logging.cfg_ file declared in _karaf-profile-example-registry_ which is always been neglected regardless if you build _karaf-profile-example-dynamic_ or _karaf-profile-example-static:_
{noformat}
[INFO] Writing configurations
[INFO] adding config file: etc\bank2.xml
[INFO] adding config file: etc\org.ops4j.pax.web.cfg
[INFO] adding config file: etc\loanBroker.xml
[INFO] adding config file: etc\jetty.xml
[INFO] adding config file: etc\profile.cfg
[INFO] adding config file: etc\bank3.xml
[INFO] not changing existing config file: etc\org.ops4j.pax.logging.cfg
[INFO] adding config file: etc\version.cfg
[INFO] adding config file: etc\bank1.xml{noformat}
> Existing configfiles (in kar) may be overwritten when building assembly
> -----------------------------------------------------------------------
>
> Key: KARAF-5678
> URL: https://issues.apache.org/jira/browse/KARAF-5678
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.0.M2
> Reporter: Grzegorz Grzybek
> Assignee: Grzegorz Grzybek
> Priority: Major
> Fix For: 4.2.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)