[
https://issues.apache.org/jira/browse/DERBY-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982898#action_12982898
]
Myrna van Lunteren commented on DERBY-4656:
-------------------------------------------
>From a discussion in this thread:
http://mail-archives.apache.org/mod_mbox/db-derby-user/201101.mbox/%[email protected]%3E,
it appears that indeed the problem is that the derby (ui/doc) plugins have
been built with java 6.
I built the ui/doc plugin the last time (10.6.1.0 time frame), and it's been
copied unchanged after that (10.6.2.1 and 10.7.1.1), so I'll check the
instructions/process (which I think date from before jdk 1.6) and investigate
and experiment.
Can/should we wait until the next release of derby?
As the ui/doc plugin is not directly related to the core plugin and/or rest of
derby, once I fix the process/instructions, I could increase the version of the
ui plugin (which would then be the only factual change), and build it (with
1.5)...
Not sure where/how to place the resulting file if not in a release.
The workaround with the current 1.1.2 ui/doc plugin is to add java 6 to the set
of jvms used in eclipse - not sure if you need to make java 6 the first in the
jvms, but that shouldn't be too much of a hassle.
> The same issue like in 4192 -> "The chosen operation is not currently
> available"
> --------------------------------------------------------------------------------
>
> Key: DERBY-4656
> URL: https://issues.apache.org/jira/browse/DERBY-4656
> Project: Derby
> Issue Type: Sub-task
> Components: Eclipse Plug-in
> Affects Versions: 10.5.3.0
> Environment: Eclipse Java EE IDE for Web Developers. Build id:
> 20100218-1602
> Reporter: Rumen Traykov
>
> The same issue like in 4194 and version 10.5.1.0. I cannot add apache derby
> nature to my project.
> "The chosen operation is not currently available"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
