I missed the last comment in the below JIRA issue. I changed Eclipse to run on Java 6 (instead of 5) and everything works. Eclipse was reporting an exception indicating that the version of the class file was not supported.
Can we compile these plugins against Java 5 to avoid this problem going forward?
Myrna,Thanks for your reply. This message seems pretty common in Eclipse in general so it is hard to tell if it is a Eclipse, Spring or Derby issue. I did find a similar issue in the Derby Jira from May of this year:If I find a way to get around this issue, I'll be sure to post it here. If there is someone on this forum however that has already figured it out, please share.Regards,JoshuaOn Mon, Jan 17, 2011 at 1:49 PM, Myrna van Lunteren <email@example.com> wrote:
Hi Joshua,On Sun, Jan 16, 2011 at 1:43 PM, Joshua White <firstname.lastname@example.org> wrote:
> I am using SpringSource Tool Suite (sts-2.5.2) which is based on Eclipse
> 3.6.1 running on Java 1.6.0_23. I have installed the derby core plugin
> (derby_core_plugin_10.7.1) and the derby ui plugin
> (derby_ui_doc_plugin_1.1.2) based on the directions here:
> When I start STS/Eclipse, I create a new Java project and attempt to add the
> Derby project nature to it, I receive the following message:
> "The chosen operation is not currently available."
> Is there a work around available for this issue?
That message is not a message from derby nor the plugin. We know the
plugin works with full eclipse; that doesn't mean it works with every
tool based on eclipse.
Did you ask the SpringSource forum?
Did you ask eclipse? Did you try the plugin with full eclipse?
A quick web search seems to hint at other plugins having troubles with
SpringSource and natures. So perhaps it doesn't support the concept of
a 'nature', which is how the derby plugin works. But I'm guessing