Can't use JFace and SWT in eclipse without creating plugin?

IProgressMonitor interface is not available in those two jars you use. You also need to put org.eclipse.equinox. Common plugin on your classpath IProgressMonitor can be used without whole eclipse environment running.

IProgressMonitor interface is not available in those two jars you use. You also need to put org.eclipse.equinox. Common plugin on your classpath.

IProgressMonitor can be used without whole eclipse environment running.(This is solution from the article you refer to. I originally thought that IProgressMonitor is in org.eclipse.core. Runtime plugin, but it has been moved to org.eclipse.equinox.

Common as described in bug #122935).

Thanks - I managed to understand that, but it took a while as in that article their talking about MANIFEST file which I do not have since I a am on plain java. So I just went on and added a reference to org.eclipse.equinox. Common and it fixed it (started throwing another error about EventManager actually but fixed it referencing org.eclipse.core.

Commands). I found this very confusing ... I should get some warnings if some of the stuff I need to run the app is missing. – JohnIdol Dec 23 '09 at 14:15 It is indeed confusing.

If you were developing eclipse plugin, you would get all warnings, since plugin dependencies are written in MANIFEST. MF file. Ff you directly referenced some class/interface that is missing, you would also get warning.

But using jar files in standalone application is tricky, and you need to hunt dependencies on your own (or use something like Ivy or Maven). – Peter Štibraný Dec 23 '09 at 14:27.

Echoing Peter's point above, I always have to add a bunch of JARs to get things running (especially for JFace). Typically, I'll need . /org.eclipse.core.

Commands_3.3.0. I20070605-0010. Jar .

/org.eclipse.core. Runtime_3.3.100. V20070530.

Jar . /org.eclipse.equinox. Common_3.3.0.

V20070426. Jar . /org.eclipse.

Jface_3.3.1. M20070910-0800b. Jar .

/org.eclipse. Osgi_3.3.2. R33x_v20080105.

Jar . /org.eclipse.ui. Forms_3.3.0.

V20070511. Jar You can use something like jarfinder to help spot what files live in what JARs.In windows I seem to remember using the find feature to look for, say, IProgressMonitor. Class in zip/jar files under the eclipse folder on the file system - as sometimes the actual JARs can be hard to track down.

I usually work by seeing what fails, tracking down / adding the JAR, rinse and repeat. Doing RCP/plugins seems like Eclipse takes care of a lot of the issues for you, doing your own stand alone app comes with this extra baggage but its really nice to have a proper stand-alone native looking GUI if you stick with it. So I typically setup vanilla (non-plugin) eclipse projects and it forces you to confront these issues (add JARs to the classpath manually).

It also comes in handy as and when you want to distribute your project.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.