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 <[EMAIL PROTECTED]> 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.
