Hi, JB, 1. I have tried obr:deploy in Karaf. It has no problem. For ACE part, do you mean that the dependency bundle (Bundle B) will be added into ACE UI (Client) - Artifacts panel when I add a bundle (Bundle A) manually also in ACE UI? I try to add bundles (Bundle A depends on Bundle B) into OBR and use ACE UI to add it the bundle A into Artifact panel in ACE UI. It seems that the Bundle B is not added into ACE UI Artifact panel.
2. Do you mean that the dependency bundle (Bundle B) will be provisioned into targets when we uses ACE to provision a bundle (Bundle A)? If yes, if the dependency bundles could be removed after we remove the provisioned bundle in ACE UI? If ACE could not auto-resolve all of dependency bundles, it means that we need to add all of bundles of an application including 3rd library bundles into ACE and provision all of them to targets. The purpose is that we intends to use Karaf to build a cluster and try to figure out the overall picture from development, build, deployment, provision. If no ACE, an provision tool, it means that we should leverage other tools like puppet for provision. But, we know that ACE is for target-base provision. For a cluster, it seems no support as you replied at #3. For Cellar, we know that we could deploy bundles with cluster:obr-deploy. Then, all bundles could be auto deploy to all of nodes of a cluster. So, we are thinking what ACE could help. Any advise for the whole process (Maven -> Jenkins -> Deploy -> Provision -> Cellar) is welcome. Thanks. -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-ACE-OBR-Usage-Scenario-tp4039625p4039668.html Sent from the Karaf - User mailing list archive at Nabble.com.
