HI Pete, I appreciate your reply and my apologies for the late reply! Would you mind sharing your tooling information with me please? A detailed step by step information of how you set your environment up will be great.
I'm still trying to find the optimum way setting this up for my client. Any detailed info will be great. For instance I'm starting with pax construct as well. Using Pax exam for my itests. Also I would like to determine best/easy way to debug the apps and looks like you have found a nice way (which I would like to follow as well) to do so. Any detailed info from you how you set up your tooling will be great! Thanks Matt On Tue, Apr 26, 2011 at 5:33 AM, Pete Carapetyan <[email protected]>wrote: > >> > I want to be able to provision all the bundles from within Eclipse IDE >> and start and debug my application? What are my options? >> > Is remote debugging with PAX -EXAM my only option? Whats the standard >> practice? How do people perform this? >> >> Typically I develop in eclipse using mvn eclipse:eclipse; import >> existing projects. Start the OSGi environment with remote debugging >> enabled and attach a remote debugger from the Eclipse IDE. This might >> not be perfect but works quite well for me since I'm switching between >> various IDE's. In addition i'm using Karaf and the dev:watch command >> does a lot of work for me. But maybe some ppl sticking only with >> eclipse have some better ideas here. >> > > Again my reply may be borderline off topic as I started with pax-exam and a > pax-construct project structure and moved after a few months to running > everything with straight PDE from within eclipse. > > I use only eclipse and no other IDE, and I avoid eclipse:eclipse like the > plague because it maintains dual competing metadata in both .classpath files > and pom.xmls. (with more competing data inside MANIFEST) Instead I rely on > both the m2eclipse plugin - a fantastically well maintained tool - and also > on Neil Bartlett's BndTools plugin. The latter can be especially helpful but > I had to get some help learning how to use it to my advantage. > > The above combination, plus the move to use straight OSGi bundles (see > separate post) whenever possible, all combined has provided me a very > productive working environment where I am able to run, debug, test, and > provision in an easy fluid fashion. Since it's an RCP app, I run everything > from within eclipse runtime. > > I still have some dual competing metadata issues between the manifest, > poms, and the bnd file, but this has all but disappeared as an issue, once I > got my templates in order (started with pax construct created projects) they > all seem to work together fine. > > I had to get outside help a couple of times to get me through some sticky > runtime strangeness. It is an extremely helpful system but far from > intuitive at times, so the help that is available from the runtime tool may > not be obvious, and thus not help you until shown by others. > > Again all this is my 2c only, your mileage may vary considerably. > > I also use spring for my IOC of services between bundles - but have also > tried the acute service injection as well and it did work. > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > >
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
