Hi, well the reployment is prohibited by the internal structure of the FileInstaller. If the file in question fails to be installed it's put on a "blacklist" inside the FileInstaller.
Now regarding your deployment scenario. A feature dependent on another feature should be able to resolve the other feature, if it's not capable of doing so it'll fail as it does right now. A kar was meant for simple deployment of a list of bundles together with a features.xml for starting those and resolving dependencies. So I'm not sure if deploying 3 kars is a good idea for this. regards, Achim 2012/7/27 helander <[email protected]>: > Before starting up my system I have placed 3 different KAR files in the > deploy directory. Lets call them kar1, kar2 and kar3. kar1 depends on > features in kar2 and kar3 depends on features in kar2. > From the logs it seems like the following happens: > -The system tries to install kar1, but it fails because the dependencies > from kar2 are not available yet > -The system tries to install kar2, but it fails because the dependencies > from kar3 are not available yet > -The system tries to install kar3 and that works (because there are no > "unknown" dependencies) > - ... and here nothing more happens > > Why does not the system retry installing the KAR:s that failed ? > > Is the described scenario complying with the semantics as defined by Karaf > 2.2.8? > > If so, how could you deal with KAR:s with dependencies to other KAR:s? > > > Thanks > > Lars > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/KAR-Deployment-order-problem-tp4025351.html > Sent from the Karaf - User mailing list archive at Nabble.com. -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
