Comments on: Eclipse Madness – Why do fragment plugins work for some Developers and not others? http://agilepainrelief.com/notesfromatooluser/2007/07/eclipse-madness.html?utm_source=rss&utm_medium=rss&utm_campaign=eclipse-madness Best practices for your goals Wed, 09 May 2012 22:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Ian Skerrett http://agilepainrelief.com/notesfromatooluser/2007/07/eclipse-madness.html/comment-page-1#comment-264 Ian Skerrett Tue, 30 Nov 1999 00:00:00 +0000 http://agilepainrelief.com/2007/07/eclipse-madness/#comment-264 Mark Not sure if you have asked this question on one of the newsgroups or the #eclipse IRC channel. Someone there might be able to help. Mark

Not sure if you have asked this question on one of the newsgroups or the #eclipse IRC channel. Someone there might be able to help.

]]> By: Neil Bartlett http://agilepainrelief.com/notesfromatooluser/2007/07/eclipse-madness.html/comment-page-1#comment-265 Neil Bartlett Tue, 30 Nov 1999 00:00:00 +0000 http://agilepainrelief.com/2007/07/eclipse-madness/#comment-265 Here's one thing you can do. First launch your test runtime with the -console command: this will bring up the internal OSGi console. You might also have to specify -noExit to prevent Eclipse from shutting down when the testrunner application finishes. Once this is done, you should see an "osgi>" prompt. Type "ss" (short status) to get a list of bundles, and find your host bundle. Check the state - if it says "INSTALLED" then there was a problem resolving it, possibly due to missing dependencies. Try typing "diag N" where N is the bundle ID number that appears in the left hand column next to your host bundle. That should tell you everything you need to know about why the bundle was not resolved. If you have any questions, feel free to email me or login to #eclipse on IRC. Regards Neil Here’s one thing you can do. First launch your test runtime with the -console command: this will bring up the internal OSGi console. You might also have to specify -noExit to prevent Eclipse from shutting down when the testrunner application finishes.

Once this is done, you should see an “osgi>” prompt. Type “ss” (short status) to get a list of bundles, and find your host bundle. Check the state – if it says “INSTALLED” then there was a problem resolving it, possibly due to missing dependencies. Try typing “diag N” where N is the bundle ID number that appears in the left hand column next to your host bundle. That should tell you everything you need to know about why the bundle was not resolved.

If you have any questions, feel free to email me or login to #eclipse on IRC.

Regards
Neil

]]> By: Mark Levison http://agilepainrelief.com/notesfromatooluser/2007/07/eclipse-madness.html/comment-page-1#comment-266 Mark Levison Tue, 30 Nov 1999 00:00:00 +0000 http://agilepainrelief.com/2007/07/eclipse-madness/#comment-266 Thanks for the Reply Neil I will give a go early next week. Based on a comment in the Eclipse.Platform newsgroup I suspect that the problem lies with target workspace problems my developer was having at the time. I would think that these were orthogonal since the test plugin didn't have any dependancies but I will just be happy if the problem solves itself. Thanks for the Reply Neil I will give a go early next week. Based on a comment in the Eclipse.Platform newsgroup I suspect that the problem lies with target workspace problems my developer was having at the time.

I would think that these were orthogonal since the test plugin didn’t have any dependancies but I will just be happy if the problem solves itself.

]]>