You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Michael Baehr <co...@gmail.com> on 2007/07/03 17:36:51 UTC
Re: Eclipse plugin wierdness
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?
Michael Baehr wrote:
>
> Yes, it is indeed so that projects that have no Derby nature only give me
> the option to remove it ...
>
> Also every project (Derby nature in .project or not) offers me to stop the
> network server - which is not running ...
>
>
> Aaron Tarter wrote:
>>
>> Strange ... So, on a fresh Java project that you did not add the Derby
>> nature to yet, your context menu shows 'Remove Derby Nature'? This menu
>> option should be controlled by the nature in the .project file. The
>> .project file in the root of your newly created project should not have
>> the
>> derby nature. It should look like:
>> <natures>
>> <nature>org.eclipse.jdt.core.javanature</nature>
>> </natures>
>>
>> Then, after adding the derby nature with the menu action, you should have
>> the following:
>> <natures>
>> <nature>org.eclipse.jdt.core.javanature</nature>
>> <nature>org.apache.derby.ui.derbyEngine</nature>
>> </natures>
>>
>> Can you confirm that this is the case?
>>
>> On 5/7/07, Michael Baehr <co...@gmail.com> wrote:
>>>
>>>
>>> Hi folks,
>>>
>>> I had a working Derby plugin for quite some time, but due to the nature
>>> of
>>> my latest projects I didn't use it.
>>>
>>> Now I'm trying to work with it again, and I have plenty of problems:
>>>
>>> - Every project is handled as if the Derby nature is present and the
>>> network
>>> server has been started (meaning I have "Remove Derby nature", "Stop
>>> network
>>> server" etc. options in the context menu). I tried this also with a new
>>> empty project
>>> - Therefore, I cannot add the Derby nature to any project
>>> - If a project indeed has the Derby nature, sysinfo and ij work for
>>> these
>>> projects. The plugin still assumes that the network server is running
>>> (which
>>> is not). I can remove Derby nature from these projects via the context
>>> menu!
>>>
>>> I have the latest stable versions (and no older ones) of the plugins,
>>> started Eclipse various times with -clean. Eclipse is 3.2.2.
>>>
>>> Any clues?
>>>
>>> Michael
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Eclipse-plugin-wierdness-tf3706229.html#a10365289
>>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> Regards,
>> Aaron J Tarter
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Eclipse-plugin-wierdness-tf3706229.html#a11414807
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Eclipse plugin wierdness
Posted by Michael Baehr <co...@gmail.com>.
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
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.
Re: Eclipse plugin wierdness
Posted by Michael Baehr <co...@gmail.com>.
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#a11630770
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Eclipse plugin wierdness
Posted by Michael Baehr <co...@gmail.com>.
I was looking for some other Derby jars, but I will do so again. Once I find
a little time, I'll start with a virgin Eclipse install again to see if the
problem is there already.
If not, then it must be some other plugin that causes a conflict (though I
only have a handful and there is no Derby in them anyways).
Thanks for the help!
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#a11480918
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Eclipse plugin wierdness
Posted by Bryan Pendleton <bp...@amberpoint.com>.
> 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
Re: Eclipse plugin wierdness
Posted by Michael Baehr <co...@gmail.com>.
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.
Re: Eclipse plugin wierdness
Posted by Myrna van Lunteren <m....@gmail.com>.
> > 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
Re: Eclipse plugin wierdness
Posted by Michael Baehr <co...@gmail.com>.
Yes, I did!
Charlie Kelly wrote:
>
> Did you try starting Eclipse with the -clean option?
>
> Charlie
>
> 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?
>>
>>
>> Michael Baehr wrote:
>>
>>> Yes, it is indeed so that projects that have no Derby nature only give
>>> me
>>> the option to remove it ...
>>>
>>> Also every project (Derby nature in .project or not) offers me to stop
>>> the
>>> network server - which is not running ...
>>>
>>>
>>> Aaron Tarter wrote:
>>>
>>>> Strange ... So, on a fresh Java project that you did not add the Derby
>>>> nature to yet, your context menu shows 'Remove Derby Nature'? This
>>>> menu
>>>> option should be controlled by the nature in the .project file. The
>>>> .project file in the root of your newly created project should not have
>>>> the
>>>> derby nature. It should look like:
>>>> <natures>
>>>> <nature>org.eclipse.jdt.core.javanature</nature>
>>>> </natures>
>>>>
>>>> Then, after adding the derby nature with the menu action, you should
>>>> have
>>>> the following:
>>>> <natures>
>>>> <nature>org.eclipse.jdt.core.javanature</nature>
>>>> <nature>org.apache.derby.ui.derbyEngine</nature>
>>>> </natures>
>>>>
>>>> Can you confirm that this is the case?
>>>>
>>>> On 5/7/07, Michael Baehr <co...@gmail.com> wrote:
>>>>
>>>>> Hi folks,
>>>>>
>>>>> I had a working Derby plugin for quite some time, but due to the
>>>>> nature
>>>>> of
>>>>> my latest projects I didn't use it.
>>>>>
>>>>> Now I'm trying to work with it again, and I have plenty of problems:
>>>>>
>>>>> - Every project is handled as if the Derby nature is present and the
>>>>> network
>>>>> server has been started (meaning I have "Remove Derby nature", "Stop
>>>>> network
>>>>> server" etc. options in the context menu). I tried this also with a
>>>>> new
>>>>> empty project
>>>>> - Therefore, I cannot add the Derby nature to any project
>>>>> - If a project indeed has the Derby nature, sysinfo and ij work for
>>>>> these
>>>>> projects. The plugin still assumes that the network server is running
>>>>> (which
>>>>> is not). I can remove Derby nature from these projects via the context
>>>>> menu!
>>>>>
>>>>> I have the latest stable versions (and no older ones) of the plugins,
>>>>> started Eclipse various times with -clean. Eclipse is 3.2.2.
>>>>>
>>>>> Any clues?
>>>>>
>>>>> Michael
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Eclipse-plugin-wierdness-tf3706229.html#a10365289
>>>>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Regards,
>>>> Aaron J Tarter
>>>>
>>>>
>>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/Eclipse-plugin-wierdness-tf3706229.html#a11415679
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Eclipse plugin wierdness
Posted by Charlie Kelly <Ch...@CharlieKelly.com>.
Did you try starting Eclipse with the -clean option?
Charlie
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?
>
>
> Michael Baehr wrote:
>
>> Yes, it is indeed so that projects that have no Derby nature only give me
>> the option to remove it ...
>>
>> Also every project (Derby nature in .project or not) offers me to stop the
>> network server - which is not running ...
>>
>>
>> Aaron Tarter wrote:
>>
>>> Strange ... So, on a fresh Java project that you did not add the Derby
>>> nature to yet, your context menu shows 'Remove Derby Nature'? This menu
>>> option should be controlled by the nature in the .project file. The
>>> .project file in the root of your newly created project should not have
>>> the
>>> derby nature. It should look like:
>>> <natures>
>>> <nature>org.eclipse.jdt.core.javanature</nature>
>>> </natures>
>>>
>>> Then, after adding the derby nature with the menu action, you should have
>>> the following:
>>> <natures>
>>> <nature>org.eclipse.jdt.core.javanature</nature>
>>> <nature>org.apache.derby.ui.derbyEngine</nature>
>>> </natures>
>>>
>>> Can you confirm that this is the case?
>>>
>>> On 5/7/07, Michael Baehr <co...@gmail.com> wrote:
>>>
>>>> Hi folks,
>>>>
>>>> I had a working Derby plugin for quite some time, but due to the nature
>>>> of
>>>> my latest projects I didn't use it.
>>>>
>>>> Now I'm trying to work with it again, and I have plenty of problems:
>>>>
>>>> - Every project is handled as if the Derby nature is present and the
>>>> network
>>>> server has been started (meaning I have "Remove Derby nature", "Stop
>>>> network
>>>> server" etc. options in the context menu). I tried this also with a new
>>>> empty project
>>>> - Therefore, I cannot add the Derby nature to any project
>>>> - If a project indeed has the Derby nature, sysinfo and ij work for
>>>> these
>>>> projects. The plugin still assumes that the network server is running
>>>> (which
>>>> is not). I can remove Derby nature from these projects via the context
>>>> menu!
>>>>
>>>> I have the latest stable versions (and no older ones) of the plugins,
>>>> started Eclipse various times with -clean. Eclipse is 3.2.2.
>>>>
>>>> Any clues?
>>>>
>>>> Michael
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/Eclipse-plugin-wierdness-tf3706229.html#a10365289
>>>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>>
>>> --
>>> Regards,
>>> Aaron J Tarter
>>>
>>>
>>>
>>
>
>