Hi Alex,
it should not, else it's a bug: if you use the instance:create, it
should use the "default/standard" features set. Only instance:close
should "copy" the set from the root instance.
Let me check using the commands.
Regards
JB
On 12/07/2015 03:05 PM, Alex Soto wrote:
HI JB,
This is is not exactly what I am seeing, or maybe it is a matter of
semantics. The child instance (after creation with instance:create)
inherits the same features.cfg as the parent, which in turn was
modified from the official distribution. For example, the parent
instance is launched from Pax-Exam with :
@Configuration
public Option[] config() {
...
features(myRepo, “my-feature”),
...
Then the child features.cfg contains:
featuresRepositories = ...my-repo...
featuresBoot = my-feature ...
Maybe this is a bug, or a misunderstanding of what is supposed to happen.
Best regards
Alex soto
On Dec 5, 2015, at 12:56 AM, Jean-Baptiste Onofré <[email protected]
<mailto:[email protected]>> wrote:
Hi Alex,
instance:create creates a new instance with a default set.
instance:clone creates a new instance with the same configuration as
the parent.
Of course, once you have created the instance, before starting, you
can update the features boot directly in
instances/NAME/etc/org.apache.karaf.features.cfg configuration file.
Regards
JB
On 12/04/2015 03:59 PM, Alex Soto wrote:
Hello,
I need to launch a Karaf child instance which does not have the same
set of boot features as the parent Karaf.
Per the documentation:
"The new instance is fresh Apache Karaf instance. It uses default
configuration files set, as you install a fresh Karaf distribution.”
But the child instance seems to inherit all the boot features from
the parent. Is this possible?
Best regards,
Alex soto
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
