Details
-
Bug
-
Resolution: Done
-
Major
-
jboss-fuse-6.1
-
None
-
None
-
%
-
Description
In a Fabric profile, with an associated feature repo (versioned in maven, so pointing to something like "mvn:com.rh/myTest/1.0.0/xml/features" ), create a new version of the fabric (fabric:version-create), then edit (using git) the path to the maven repo to point to a new minor version (so something like "mvn:com.rh/myTest/1.0.1/xml/features"), and then apply this new version of the fabric to the containers.
This doesn't trigger the change in the bundles related to that feature repo (or better, looking from FMC, the version is updated, the update location is not).
Instead, changing to a new major version (so something like "mvn:com.rh/myTest/1.2.0/xml/features"), everything works as expected.
Attachments
Issue Links
- is related to
-
ENTESB-2387 Karaf command "osgi:list -l" still shows location of old bundles even after patch is installed successfully in fabric
- Closed