I think the big difference between where are may be that (for you code) you were choosing to run it as a Java Application or SWT Application. Would that be right - when I choose that option with your code (from inside my test plugin still routing through the plugin under test) it works, but when I run my test as a a plugin JUnit test it fails.
Definitely is a plugin, I'm only adjusting the build path via the MANIFEST.MF panel, and I have been using the flash UI to resolve dependancies in MANIFEST.MF but when I run my plugin tests the splash screen pops up and then I get the SEVERE problem in the console window. AJ Quoting Jerome Louvel <[EMAIL PROTECTED]>: > > Hi AJ, > > You must be missing one step. It works fine for me, without any buddy > class > loading. It is essential that you create a "Plugin-project" and not a > simple > "Java project". Then specify the dependencies in the MANIFEST.MF (nice > UI > available) and that should be all. > > I've just done the test gain and attached a sample project using the > HTTP > client (similar to tutorial example 2). Let me know if it works for > you. > > Best regards, > Jerome >
