karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4805) configfiles are not copied to system directory
Date Wed, 26 Oct 2016 19:41:59 GMT

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

ASF GitHub Bot commented on KARAF-4805:

GitHub user tterm opened a pull request:


    [KARAF-4805] configfiles are not copied to system directory

    Added the missing copy of the config files and tested it. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tterm/karaf karaf-4.0.x

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #255
commit f47e2b376b46e3dd649afa318e6da516131094c6
Author: tterm <tterm@max>
Date:   2016-10-26T19:37:11Z

    [KARAF-4805] configfiles are not copied to system directory


> configfiles are not copied to system directory
> ----------------------------------------------
>                 Key: KARAF-4805
>                 URL: https://issues.apache.org/jira/browse/KARAF-4805
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-profile
>    Affects Versions: 4.0.7
>            Reporter: Thomas Termin
> I have a feature which contain a configfile like:
> <configfile finalname='/etc/FinalFile.cfg' override="false">
>       mvn:my.package/MyArtifact/1.0.0/cfg/file-cfg
> </configfile>
> If I put the feature which contains the configfile within the
> <installedFeatures> of my custom karaf pom file, all referenced bundles
> are installed within the system directory. But the configfile is just
> ignored. That leads of course to the problem, that the installation of
> the features failed if there is no maven repository available which is
> the case for my environment.
> I will provide a pull request for it.

This message was sent by Atlassian JIRA

View raw message