As for me, my dev environment looks like this (although, I'm constantly tweeking it):
- I'm using Eclipse (SpringSource ToolSuite, more specifically, but I'm not yet actually using any of STS' OSGi/DM features). - Pax Exam: This (via Pax Runner) lets me run my bundle project as a whole just by typing 'pax-provision'. An OSGi runtime is started and all of my project's bundles are deployed and ready for me to kick the tires. - For more precise tests with minimal human involvement, I use Pax Exam to run bundle integration tests against my bundles. Pax Exam tests can be run anywhere you can run JUnit tests. None of this is a "one button in Eclipse" solution (although, I suppose running a Pax Exam test could be a one-click activity). But it's the approach I favor at the moment. > Hi, > > another question from an osgi beginner. How does your development > environment look like? I'm currently using eclipse and the maven bundle > plugin. My project is devided in several bundles / maven modules. Now, > if I'm working on a bundle and want to test it, I have to run maven and > afterwards deploy the bundle to the osgi framework, which could be done > by hand or by running a file monitoring bundle like "File install". But > this is not comfortable enough for me. I want to hit _one_ button in > eclipse and everything should be done as fast as possible. How do I > achieve that, is there a way? > > Regards > Henrik > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
