db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Baehr <code...@gmail.com>
Subject Re: Eclipse plugin wierdness
Date Fri, 27 Jul 2007 09:12:03 GMT

As suspected, there was a problem with the Groovy plugin. It has been
corrected, and since then the Derby plugin works again.

Sorry for the noise ...


Michael Baehr wrote:
> Ok, seems that I'm about to nail the problem.
> It looks like it is a conflict with another plugin, the Groovy (see
> groovy.codehaus.org) plugin! As soon as I install it, the Derby plugins
> stops working and shows the symptoms I described.
> I just mailed on the Groovy plugin mailing list, let's see what they come
> up with!
> I'll keep you posted.
> Michael
> Bryan Pendleton wrote:
>>> Well, as I was installing Eclipse 3.3 I decided to only import the
>>> projects
>>> I'm actually working on and leave the other ones in the old workspace.
>>> None of the imported projects has anything to do with Derby, especially
>>> none
>>> has the Derby nature.
>>> I just created a new empty workspace, then created a new empty Java
>>> project
>>> in it.
>>> The Derby context menu again offers me to remove the Derby nature of the
>>> new
>>> project and to stop the (not running) network server ... :-(
>> Is there any chance that the Derby plugin jars got copied to some magic
>> place
>> such as the "lib/ext" subdirectory of your JRE. That would cause them to
>> be found unexpectedly in the class path for all projects.
>> You could try using something like -verbose:class when running Eclipse,
>> to
>> try to get some information on where the Derby classes are being loaded
>> from,
>> or perhaps use a file-monitoring tool like the Sysinternals FileMon tool
>> (on
>> Windows) to observe file access at the OS level.
>> thanks,
>> bryan

View this message in context: http://www.nabble.com/Eclipse-plugin-wierdness-tf3706229.html#a11825425
Sent from the Apache Derby Users mailing list archive at Nabble.com.

View raw message