karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Achim Nierbeck (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KARAF-1549) Child instance features cfg file looks weird
Date Thu, 23 May 2013 14:55:20 GMT

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

Achim Nierbeck resolved KARAF-1549.

    Resolution: Fixed

After thinking about this some more and starting a philosophical discussion with myself I
came to the conclusion, that the current fix 

Author: anierbeck
Date: Thu May 23 14:51:04 2013
New Revision: 1485746

URL: http://svn.apache.org/r1485746

should be enough :)

If one want's a exact replicate of the root instance one needs to do the clone command. If
that isn't the case the person using the create needs to make sure he knows beforehand what
kind of boot features are required. 

Usually the clone of the root should be sufficient :D
> Child instance features cfg file looks weird
> --------------------------------------------
>                 Key: KARAF-1549
>                 URL: https://issues.apache.org/jira/browse/KARAF-1549
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature, karaf-instance
>    Affects Versions: 3.0.0
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Achim Nierbeck
>             Fix For: 3.0.0
>         Attachments: karaf-3.0_1549.diff
> In a child instance, the etc/org.apache.karaf.features.cfg file looks weird, and completely
different from the root instance:
> featuresBoot=config,ssh
> featuresRepositories=mvn\:org.apache.karaf.features/standard/3.0.0-SNAPSHOT/xml/features,mvn\:org.apache.karaf.features/enterprise/3.0.0-SNAPSHOT/xml/features
> More over, the etc/org.apache.karaf.features.obr.cfg and etc/org.apache.karaf.features.repos.cfg
files are not present in the child instances, whereas they should be here.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message