eclipse-rcp

I have developed one eclipse RCP application which I am calling from my own Java program. When I run my own Java program from command prompt (windows) it is perfectly working and giving the results. But when I have integrated with the ant build script in eclipse 3.2 it is giving the following problem: !ENTRY org.eclipse.core.launcher 4 0 Dec 02, 2009 10:53:17.608 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.RuntimeException: Could not find framework at org.eclipse.core.launcher.Main.getBootPath(Main.java:395) at org.eclipse.core.launcher.Main.basicRun(Main.java:174) at

In order to use the instrumentation features introduced in JDK 5, you can use the -javaagent flag passed to the JVM. This will inject an instance of an Instrumentation class into the static premain method. For example in a class like this: public class MyClass { public static Instrumentation inst; public static void premain(String options, Instrumentation inst) { MyClass.inst = inst; } } With an appropriate manifest file, you can run this as follows: java -javaagent:myfiles.jar SomeClass This calls the premain method then main from SomeClass . This approach is used in the Java.SizeOf Project

I'm working on a plugin project in which I'm using Eclipse background processing. What's the difference between the syncExec() and asyncExec() methods of the Display class? In which situations are they applicable? Any example could be helpful. Tom Seidel from Q: Why do I get the error "org.eclipse.swt.SWTException: Invalid thread access"? To allow background threads to perform operations on objects belonging to the UI-thread, the methods syncExec(Runnable runnable) and asyncExec(Runnable runnable) of Display are used. These are the only methods in SWT that can be called from any thread. They

I got the below exception while trying to run an eclipse product which exported without errors java.lang.NullPointerException at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.<init> any clue? Full stack trace: !SESSION 2013-07-23 02:08:52.676 ----------------------------------------------- eclipse.buildId=unknown java.version=1.7.0_21 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.osgi 4 0 2013-07-23 02:08:54.202 !MESSAGE Application error !STACK 1 java.lang

In order to be able to use my Eclipse plugin "treezCore" also as a Java9 module I created a module-info.java in my src folder. Furthermore, I moved the Plug-in Dependencies from the Classpath to the Modulepath. I can see a module "org.eclipse.swt.3.106.1.v20170926" in the plugin dependencies: However, I am not able to reference that module in my module-info.java. I tried require org.eclipse.swt.3.106.1.v20170926; require org.eclipse.swt; require swt; None of those options worked. The jar file \plugins\org.eclipse.swt_3.106.1.v20170926-0519.jar that is used by Eclipse does not contain a module

I'm just starting with OSGi and Eclipse RCP. Could someone explain to me the difference between "Eclipse" and "Equinox" as the target platform, when creating a new eclipse plugin project? I still know that Equinox is Eclipse's implementation of OSGi. I read in some articles that eclipse rcp is also based on Equinox. So where is the difference between the target platform you have to choose in a new Eclipse Plugin Project? Best regards It is about the environement in which the module you will be creating will run: see this Vogalla's RCP Tutorial Vogella's OSGi with Eclipse Equinox Eclipse

How to use log4j logging API in an Eclipse RCP project? As a workaround U tried to create a new OSGI Bundle which has a log4j jars, below is the bundle structure: I've crated a basic RCP application with a view (template) named loggingtest .I've included the bundle log4j in the dependencies tab of loggingtest project.In the Activator start method i placed the following code Logger logger = Logger.getLogger(Activator.class); logger.info("Info starting"); logger.warn("Warning starting"); logger.error("Error starting"); so everything is fine so far I'm able to use log4j API and half way through,i