karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KARAF-2266) Warn and override when feature can not install files
Date Wed, 12 Aug 2015 04:48:46 GMT

     [ https://issues.apache.org/jira/browse/KARAF-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jean-Baptiste Onofré updated KARAF-2266:
    Fix Version/s:     (was: 4.0.1)
                       (was: 3.0.5)

> Warn and override when feature can not install files
> ----------------------------------------------------
>                 Key: KARAF-2266
>                 URL: https://issues.apache.org/jira/browse/KARAF-2266
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-feature
>    Affects Versions: 3.0.0.RC1
>            Reporter: Christian Schneider
>            Assignee: Jean-Baptiste Onofré
> karaf can deploy files like config files during the installation of a feature. If the
file is already present then it is not overwritten.
> I wonder if we should print a warning in this case. One use case for this is a new version
of a feature that adds a new needed property
> to a config file. If the old feature was already present then the old config will be
present and the user may also have done changes.
> So there might be cases where a feature works if it can install its default configs but
does not work when they are already present but invalid.
> So we could write for each file that is already present:
> "Warning: file <path> to be deployed is already present and will not be changed."
> We could also provide an option in feature:install like -f that forces all files to be
overwritten if someone wants to make sure the feature installation should use the defaults.

This message was sent by Atlassian JIRA

View raw message