-
1. Re:
nickboldt May 28, 2009 6:29 PM (in response to mstille)Since JBDS 2.0 is built with Eclipse 3.4.2 and JBT 3.0 pieces, it should be seamlessly intercompatible with JBT 3.0 itself. No pun intended.
Check your workspace/.metadata/.log file or the Error view for more information on what that NPE really means.
You might also want to try pointing JBDS at a brand-new empty workspace, then using File > Import to bring your old project into the new workspace.
Finally, if that doesn't work, compare a project created in JBDS with your old project. One might have different settings in the .classpath or .project file which is causing a problem. (To see these files in Eclipse or JBDS, open the Navigator view.) -
2. Re:
mstille May 29, 2009 12:22 PM (in response to mstille)Thank you very much!
In the log file, there was a java.lang.NullPointerException at org.drools.eclipse.util.DroolsRuntimeManager.getDroolsRuntimeJars(DroolsRuntimeManager.java:187), so I removed reference to drools from .classpath. And it works! -
3. Migrating from JBoss Tools to JBoss Dev Studio (Drools suppo
nickboldt May 29, 2009 5:36 PM (in response to mstille)If you actually want to use Drools in JBDS, you can install it from the JBoss Tools Stable update site:
Instructions: http://www.jboss.org/tools/download/update.html
Site to use: http://download.jboss.org/jbosstools/updates/stable/ -
4. Re:
maxandersen May 31, 2009 1:34 PM (in response to mstille)"mstille" wrote:
Thank you very much!
In the log file, there was a java.lang.NullPointerException at org.drools.eclipse.util.DroolsRuntimeManager.getDroolsRuntimeJars(DroolsRuntimeManager.java:187), so I removed reference to drools from .classpath. And it works!
Please report in jira with a full stacktrace and what you exactly removed to fix it...there should not be any NPE when migrating workspaces...