The latest Dr Java plugin v0.9.5 for Eclipse does not
load when I restart the workbench. It does not appear
in the perspectives list or in the preferences menu.
However, 0.9.4 works properly.
Windows XP Professional (SP1)
Eclipse 3.0.1
Dr. Java Plugin 0.9.5
Java 1.4.2
Logged In: YES
user_id=678210
Edit plugin.xml, modify
<requires>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.debug.ui"/>
<import plugin="org.eclipse.jdt.ui"/>
<import plugin="org.eclipse.jdt.core"/>
<import plugin="org.eclipse.console.ui"/>
</requires>
to
<requires>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.debug.ui"/>
<import plugin="org.eclipse.jdt.ui"/>
<import plugin="org.eclipse.jdt.core"/>
<import plugin="org.eclipse.ui.console"/>
<import plugin="org.eclipse.core.runtime.compatibility"/>
<import plugin="org.eclipse.search"/>
</requires>
and then restart Eclipse with -clean parameter. It will work
fine.
Logged In: YES
user_id=429731
Unfortunately, I'm running into other issues with the workaround
jiayun posted, at least on Linux. The DrJava perspective appears
again in the menu, but opening it causes Eclipse 3.0 to crash.
I'm also having no luck trying this fix on OS X, where I can't easily
specify the -clean parameter.
Any leads on what is causing the problem, and whether -clean
makes a difference?
Charlie
Logged In: YES
user_id=697810
Indeed, this is the case. Somehow Eclipse 3.0.0 was okay
with the mistakes in the plugin.xml. Thanks for the fix,
and I will look into the reason that it still seems to be
failing on Macs.
Logged In: YES
user_id=431096
I was able to enable the Interactions view on Mac OS X 10.3.5 by first
launching eclipse via Terminal (with the -clean param), then relaunching
normally. However, it is also hanging Eclipse for me.
0.9.4 at least gives some error feedback, in the form of an unhandled
exception:
!ENTRY org.eclipse.ui 4 0 Sep 29, 2004 20:25:58.908
!MESSAGE Can't start the AWT because Java was started on the first
thread. Make sure StartOnFirstThread is not specified in your
application's Info.plist or on the command line
!STACK 0
java.lang.InternalError: Can't start the AWT because Java was started on
the first thread. Make sure StartOnFirstThread is not specified in your
application's Info.plist or on the command line
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1503)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:
50)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.loadLibraries(Toolkit.java:1437)
at java.awt.Toolkit.<clinit>(Toolkit.java:1458)
at java.awt.Color.<clinit>(Color.java:250)
at
edu.rice.cs.drjava.config.OptionConstants.<clinit>(OptionConstants.java:
102)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at
edu.rice.cs.drjava.config.OptionMapLoader.class$(OptionMapLoader.java:
59)
at
edu.rice.cs.drjava.config.OptionMapLoader.<clinit>(OptionMapLoader.java
:59)
at
edu.rice.cs.drjava.config.SavableConfiguration.loadConfiguration(Savable
Configuration.java:78)
at
edu.rice.cs.drjava.config.FileConfiguration.loadConfiguration(FileConfigura
tion.java:73)
at edu.rice.cs.drjava.DrJava.initConfig(DrJava.java:298)
at edu.rice.cs.drjava.DrJava.getConfig(DrJava.java:122)
at
edu.rice.cs.drjava.model.repl.newjvm.MainJVM.startInterpreterJVM(MainJ
VM.java:703)
at
edu.rice.cs.drjava.plugins.eclipse.repl.EclipseInteractionsModel.<init>(Ecl
ipseInteractionsModel.java:121)
at
edu.rice.cs.drjava.plugins.eclipse.repl.EclipseInteractionsModel.<init>(Ecl
ipseInteractionsModel.java:92)
at
edu.rice.cs.drjava.plugins.eclipse.views.InteractionsView.createPartContr
ol(InteractionsView.java:175)
at org.eclipse.ui.internal.PartPane$2.run(PartPane.java:137)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.ja
va:616)
at org.eclipse.core.runtime.Platform.run(Platform.java:747)
<snip misc eclipse code/>
Logged In: YES
user_id=697810
The primary problem has been resolved, that being errors in
the plugin.xml that prevented the 0.9.5 plug-in from being
loaded. A secondary problem has also been resolved, which
is that a new, windows-specific jar was not included in the
release plug-in, but the jar is necessary to run on Windows.
The releases have been updated, but as a side-note, the
updated plugin.xml causes the plug-in to fail to load under
Eclipse 2.1, so I have added an additional release,
drjava-eclipse-0.9.5-eclipse-v2.zip, which contains the
correct version and plug-in information for Eclipse 2.1. As
mentioned before, you will almost certainly have to restart
Eclipse with the -clean parameter.
I will leave this report open until I have had a chance to
test the situation on a Mac, as the platform has always been
the biggest trouble spot, at least partially because I don't
have any Macs readily avaliable to me for testing.