Demo video showing how to use Osmorc
I have created a small demo video which gives you a quick tour around Osmorc. It explains a basic project setup, the Osmorc facet and how to create run configurations to run and debug OSGi bundles from IntelliJ. It does by far not cover all things to know about Osmorc, but it should give you a nice start.
Please provide feedback about the video, as this is my first try on such stuff and there are probably a lot of things to be improved in further videos. Looking forward to your comments.
Link: Osmorc Demo Video
Thanks for the video; it answered my run target questions.
Two issues I'm having:
1. It seems like the "Additional properties" for the manifest file lose their carriage returns on my system after awhile. I went back the next day and they were all in one row.
2. I already had a .bnd file that I was using in ant. It would be really nifty if Osmorc could use that for the "Bundle Settings" so I could keep them in sync between our ant build and the IntelliJ build by modifying one file.
Osmorc is really coming along though... keep up the great work!
If it helped out, it has served it's purpose :D. For issue 1, could you please open up a ticket in our bugtracker? Issue 2 sounds like a cool enhancement, I'll try to put that up during the week...
One more thing, I think, is keeping me from really using Osmorc full-time. We have some custom properties we set in the framework to initialize our bundles with initial settings (the first argument to the Felix objects initializer, or the configuration/config.ini file in Equinox). Osmorc's run target doesn't provide a way to set such properties, and I'm not sure if there's a file somewhere that gets read.
The other non-critical enhancement is to be able to set the run level of each bundle. Since we're a GUI app, it's a lot nicer to initialize all the plugins before running the GUI bundle so things don't jump around a lot on startup.
I'll add the bug to the issue tracker.
I went ahead and added all of my suggestions (a new feature requests) and my bug (as a bug) to the issue tracker.