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 Thu, 05 Jul 2007 14:55:17 GMT

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 ... :-(

I'm clueless!

Myrna van Lunteren wrote:
>> > Michael Baehr wrote:
>> >> I just installed Eclipse 3.3, with no non-standard plugins and a fresh
>> >> workspace.
>> >>
>> >> After installing the Derby plugin and importing some projects, I have
>> >> exactly the same effect again!
>> >>
>> >> What could be wrong with my system outside of Eclipse to cause this?
>> >>
>> >>
> It's very puzzling. You said you had the problem again after importing
> 'some' projects. Does it matter which projects?
> I'm wondering if one of the projects somehow has gotten some
> corruption in its .xml...Or whether there is something specific in it.
> If you can find projects that cause this when imported, vs. ones that
> don't, maybe you can compare the plugin xml details and find something
> that triggers eclipse/derby plugin to behave this way...
> Myrna

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

View raw message