[ https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677739#comment-15677739 ]
Guillaume Nodet commented on KARAF-4158: ---------------------------------------- Instead of using feature1, feature2, feature3. feature4 You can create sets of features: (feature1, feature3), (feature3, feature4) The features of a given (inside the parentheses) will be installed before the features of the next stage are installed. Not sure what you mean by "auto start the core internally which starts all bundle again"... > Unexpected behavior on first startup > ------------------------------------ > > Key: KARAF-4158 > URL: https://issues.apache.org/jira/browse/KARAF-4158 > Project: Karaf > Issue Type: Bug > Components: karaf-core > Affects Versions: 4.0.3 > Environment: RHEL 6.2 x32, Java 1.8.0_72-ea-b05 > Reporter: Jean-Philippe CLEMENT > Assignee: Christian Schneider > Fix For: 4.1.0, 4.0.6 > > > This problem only occurs on the very first startup of a custom assembly. This > means unpacking the assembly .tar.gz then run karaf. This issue is not 100% > reproducible. Several untar/run might be necessary to reproduce the issue. > The problem comes with Blueprint property-placeholders. User bundles might be > started and not get .cfg replaced properties but the "$(PARAM_NAME)" itself > (String property). > I suspect user bundles to be started before the .cfg files are populated in > the /etc directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)