[
https://issues.apache.org/jira/browse/DERBY-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-4656:
--------------------------------------
Attachment: DERBY-4656.diff
Attaching a patch which only modifies the instructions in the Readme, but also
increases the last digit on the ui and doc plugin versions to 1.1.3, so we have
a way of differentiating the previous (1.1.2) ui/doc version which were built
with 1.6 jvm.
I don't know how to force the ui build in eclipse to be with 1.5; if someone
does know, we can add that later.
(the doc plugin has no classes, so I think the jvm is irrelevant for that one).
Adding this first to 10.7.; I intend to up-port it to trunk.
As the actual functionality of the ui and doc plugin remains the same, and
there is no actual reference to the derby core functionality (apart from the
need to have *a* org.apache.derby.core.plugin.xml available during the build in
eclipse) a finished 1.1.3 plugin should also work with the 10.6. core plugins,
or any 10.8 core plugins when we produce a next release.
> The same issue like in 4194 -> "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
> Attachments: DERBY-4656.diff
>
>
> 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.
