Hi Richard, Thanks for the answer.
While I was using maven with OBR repository and obr gogo commands, everything was fine. But after trying to use auto-deploy directory, I found out that I have to put this to my POM: <Embed-Dependency>org.apache.felix.gogo.runtime;scope=compile|runtime</Embed-Dependency> Now auto-deploy works. Cheers, Bahadır Konu On 10 May 2011 22:12, Richard S. Hall <[email protected]> wrote: > The standard framework launcher (aka main), will install and start all > bundles contained in the "bundle/" directory by default. If you are putting > all of your bundles in there, then you should not get any resolve exceptions > since they are installed in one pass, then started in a second pass. > > If, on the other hand, you are talking about service dependencies and not > package dependencies, then it is possible the bundles won't start up in the > order you expect. But this likely means your bundles aren't coded properly. > They should not expect a particular order for service startup, they should > use a technique like service listeners, ServiceTracker, iPOJO, etc. to track > when services become available. > > -> richard > > > On 5/10/11 15:06, Bahadir Konu wrote: > >> Hi everybody, >> >> I have spent a lot of time trying to solve this but there seems to be >> something I cannot think of. >> >> I have an application which contains a bundle that extends gogo shell. >> This >> bundle is dependent to built-in "gogo.command" bundle under the /bundle >> directory. >> When I put my bundles under auto-deploy directory and start the framework, >> felix (it seems) tries to install my bundle before the built-in >> gogo.command >> bundle and framewok fails to start. (BundleException: requirement >> failed..) >> >> To overcome, I declared the start level of my bundles as "2" in the felix >> config file. This solves the previous problem I mentioned but there is >> another problem: >> My bundles are *not* ACTIVE. They are INSTALLED. The built-in bundles are >> active but my bundles are not! >> >> What I need is a script that starts the framework and starts my bundles. >> (One of the bundles extend gogo shell, and it is the UI of the >> application.) >> >> So, currently what I can only do is, writing the script that can only >> install the bundles. Then I ll tell user to issue START commands from the >> shell manually before using the additional gogo commands of my >> applicaiton. >> >> Is my strategy of launching incorrect? Is there another way of deploying >> and >> launching my bundles with a script? If not, how can I solve the problems >> that I mentioned? >> >> Any help is appreciated.. >> >> Cheers, >> Bahadır Konu >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
