-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
jboss-fuse-6.2.1
-
None
-
%
-
-
-
When a new child container is created from an existing ensemble, the configuration files in the <child container home>/etc directory get the default values, rather than the values set for the parent container.
Example: If all external remote repositories are removed from the configurations in a new ensemble (removed from etc/org.ops4j.pax.url.mvn.cfg, etc/io.fabric8.maven.cfg, fabric/import/fabric/profiles/default.profile/io.fabric.agent.properties) and verified removed via config:list, but then a new child container is created via container-create-child, the child gets the default etc/org.ops4j.pax.url.mvn.cfg and the default external repositories show up running config:list on the child, even though they are not listed in any profile. config:list in the parent container still shows only configured remote repos (no external repos).
- is related to
-
ENTESB-5716 Can't create child on 111, 115
- Closed
-
ENTESB-5717 Exception on creating ssh container (Could not find artifact)
- Closed
-
ENTESB-4727 container-create-child experiences long delay if mvn artefacts need to be downloaded from remote repository
- Closed
-
ENTESB-2623 urlHandler protocol "profile:" returns wrong data
- Closed
-
ENTESB-4674 jmxRole configuration not inherited from parent when creating child container
- Closed
-
ENTESB-4787 Fabric child container's initial properties should default to those of its parent
- Closed