Hi Martin, So you might be interested in Sigil (when it's available - currently in migration) http://felix.apache.org/site/apache-felix-sigil.html
I'm working on the debug support on the trunk at the moment and expect to have something functional in the next couple of weeks. The model I'm working towards is long running osgi container and hot deploy/undeploy of bundles from the workspace, including debug support etc. This used to work when Sigil was over at codecauldron and I've built the backend functionality here at apache. It's now just a matter of getting some clear time to work through the gui side of things. Regards, Dave On Wed, Aug 26, 2009 at 6:56 AM, Cornelius, Martin (DWBI)<[email protected]> wrote: > > Hi there, > > Does anybody know how to automate the development cycle of felix-bundles > in eclipse ? > > Currently, after every change in the code of the bundle under > development, i have to execute two steps manually: First recreate the > bundle by calling Bnd (via the context menu), and then erase the bundle > cache to force felix to reload the bundle at the next restart. > > Compared to 'normal' development in eclipse where just clicking the > debug button gets everything compiled and the debugger started, this > appears somewhat stone-aged to me. > > Thanks in advance for any tips, Martin > > > ************************************************ > The information contained in, or attached to, this e-mail, may contain > confidential information and is intended solely for the use of the individual > or entity to whom they are addressed and may be subject to legal privilege. > If you have received this e-mail in error you should notify the sender > immediately by reply e-mail, delete the message from your system and notify > your system manager. Please do not copy it for any purpose, or disclose its > contents to any other person. The views or opinions presented in this e-mail > are solely those of the author and do not necessarily represent those of the > company. The recipient should check this e-mail and any attachments for the > presence of viruses. The company accepts no liability for any damage caused, > directly or indirectly, by any virus transmitted in this email. > ************************************************ > > --------------------------------------------------------------------- > 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]
