Derby
  1. Derby
  2. DERBY-4194 10.5 RC1 and RC2 ui plugin doesn't work properly
  3. DERBY-4656

eclipse ui/doc plugin 1.1.2 was built with 1.6 jvm, results in "The chosen operation is not currently available" on Add Derby Nature with 1.5 jvms

    Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.5.3.0
    • Fix Version/s: 10.7.1.4, 10.8.1.2
    • Component/s: Eclipse Plug-in
    • Labels:
    • Environment:
      Eclipse Java EE IDE for Web Developers. Build id: 20100218-1602
    • Urgency:
      Normal

      Description

      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"

      1. derby_ui_doc_plugin_1.1.3.zip.md5
        0.0 kB
        Myrna van Lunteren
      2. derby_ui_doc_plugin_1.1.3.zip.asc
        0.2 kB
        Myrna van Lunteren
      3. derby_ui_doc_plugin_1.1.3.zip
        859 kB
        Myrna van Lunteren
      4. DERBY-4656.diff
        2 kB
        Myrna van Lunteren

        Activity

        Hide
        fpientka added a comment -

        Warning because of old-style is perhapse the reason that Add Derby Nature doesn't work wihr Kepler 4.3
        MESSAGE Unhandled event loop exception
        !STACK 0
        java.lang.NullPointerException
        at org.apache.derby.ui.popup.actions.AddDerbyNature.run(AddDerbyNature.java:137)
        at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
        !MESSAGE The plugin "org.apache.derby.plugin.doc" with the version "1.1.3" and location "reference:file:plugins/org.apache.derby.plugin.doc_1.1.3/" is an old style Eclipse 2.0 plugin with no OSGi bundle manifest. Support for Eclipse 2.0 style plugins will be removed in a future release. Refer to the migration guide for details.
        !ENTRY org.eclipse.osgi 2 0
        !MESSAGE The plugin "org.apache.derby.ui" with the version "1.1.3" and location "reference:file:plugins/org.apache.derby.ui_1.1.3/" is an old style Eclipse 2.0 plugin with no OSGi bundle manifest. Support for Eclipse 2.0 style plugins will be removed in a future release. Refer to the migration guide for details.

        Show
        fpientka added a comment - Warning because of old-style is perhapse the reason that Add Derby Nature doesn't work wihr Kepler 4.3 MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at org.apache.derby.ui.popup.actions.AddDerbyNature.run(AddDerbyNature.java:137) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251) !MESSAGE The plugin "org.apache.derby.plugin.doc" with the version "1.1.3" and location "reference: file:plugins/org.apache.derby.plugin.doc_1.1.3/ " is an old style Eclipse 2.0 plugin with no OSGi bundle manifest. Support for Eclipse 2.0 style plugins will be removed in a future release. Refer to the migration guide for details. !ENTRY org.eclipse.osgi 2 0 !MESSAGE The plugin "org.apache.derby.ui" with the version "1.1.3" and location "reference: file:plugins/org.apache.derby.ui_1.1.3/ " is an old style Eclipse 2.0 plugin with no OSGi bundle manifest. Support for Eclipse 2.0 style plugins will be removed in a future release. Refer to the migration guide for details.
        Hide
        Knut Anders Hatlen added a comment -

        [bulk update] Close all resolved issues that haven't been updated for more than one year.

        Show
        Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.
        Hide
        Myrna van Lunteren added a comment -

        I'm resolving this issue. The zip 1.1.3 ui/doc plugin I created is now only available in this jira issue; it can be picked up from here for the next derby release vehicle and copied around as needed.

        Show
        Myrna van Lunteren added a comment - I'm resolving this issue. The zip 1.1.3 ui/doc plugin I created is now only available in this jira issue; it can be picked up from here for the next derby release vehicle and copied around as needed.
        Hide
        Myrna van Lunteren added a comment -

        Attaching a ui/doc plugin.zip file built with ibm 1.5, and also attaching the signed (pgp and md5) files to match.
        This file can be used instead of the ui/doc 1.1.2.zip file when only a 1.5 jvm is available.
        We can use this zip file for a 10.8 release - unless there will be real functional changes to the plugin, which doesn't seem likely at this point in time.

        Show
        Myrna van Lunteren added a comment - Attaching a ui/doc plugin.zip file built with ibm 1.5, and also attaching the signed (pgp and md5) files to match. This file can be used instead of the ui/doc 1.1.2.zip file when only a 1.5 jvm is available. We can use this zip file for a 10.8 release - unless there will be real functional changes to the plugin, which doesn't seem likely at this point in time.
        Hide
        Myrna van Lunteren added a comment -

        committed with revision 1061570 to 10.7, and up-ported with revision 1061576 to trunk.

        Show
        Myrna van Lunteren added a comment - committed with revision 1061570 to 10.7, and up-ported with revision 1061576 to trunk.
        Hide
        Myrna van Lunteren added a comment -

        modifying the title to facilitate searching.

        Show
        Myrna van Lunteren added a comment - modifying the title to facilitate searching.
        Hide
        Myrna van Lunteren added a comment -

        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.

        Show
        Myrna van Lunteren added a comment - 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.
        Hide
        Myrna van Lunteren added a comment -

        From a discussion in this thread:
        http://mail-archives.apache.org/mod_mbox/db-derby-user/201101.mbox/%3CAANLkTin7n1jXHTrRu1-Gn1E8ivkUy6t7KR7eVaaTV0fX@mail.gmail.com%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.

        Show
        Myrna van Lunteren added a comment - From a discussion in this thread: http://mail-archives.apache.org/mod_mbox/db-derby-user/201101.mbox/%3CAANLkTin7n1jXHTrRu1-Gn1E8ivkUy6t7KR7eVaaTV0fX@mail.gmail.com%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.
        Hide
        Rodrigo Lemos added a comment -

        Sadly, derby plugins were compiled with Java 6. Please check if you are running under Java 1.5.

        Show
        Rodrigo Lemos added a comment - Sadly, derby plugins were compiled with Java 6. Please check if you are running under Java 1.5.
        Hide
        T C added a comment - - edited

        The exact same thing is happening to me, using org.apache.derby.core_10.6.1 and org.apache.derby.ui_1.1.2. I have installed this into eclipse galileo 3.5 (specific build info 20090621-0832) other packages I have installed:
        com.icesoft.ide.eclipse.icefaces.facelets.feature.feature.group version 3.6.2.20091001203,
        com.icesoft.ide.eclipse.icefaces.core.feature.feature.group version 3.6.2.20091001203,
        org.eclipse.jst.jsf.facelet.feature.feature.group 0.2.0.200910012033

        The exact steps are: create a new java project, then right click on project choose "Apache Derby" then "add Apache Derby nature". An error dialog pops up with the message "The chosen operation is not currently available".

        The same exact behavior occurs with a dynamic web project instead of a pure java project.

        Show
        T C added a comment - - edited The exact same thing is happening to me, using org.apache.derby.core_10.6.1 and org.apache.derby.ui_1.1.2. I have installed this into eclipse galileo 3.5 (specific build info 20090621-0832) other packages I have installed: com.icesoft.ide.eclipse.icefaces.facelets.feature.feature.group version 3.6.2.20091001203, com.icesoft.ide.eclipse.icefaces.core.feature.feature.group version 3.6.2.20091001203, org.eclipse.jst.jsf.facelet.feature.feature.group 0.2.0.200910012033 The exact steps are: create a new java project, then right click on project choose "Apache Derby" then "add Apache Derby nature". An error dialog pops up with the message "The chosen operation is not currently available". The same exact behavior occurs with a dynamic web project instead of a pure java project.
        Hide
        Myrna van Lunteren added a comment -

        Interesting, because DERBY-4194 was fixed by regenerating the ui/doc plugin, and it hasn't changed since. I tested the 10.5.3.0 plugin(s) with eclipse galileo 3.5 (& documented it at the time on the testing page: http://wiki.apache.org/db-derby/DerbyTenFiveThreeRelease).

        It would help if you could provide a detailed description of all the steps taken, including exact versions & (location of) packages of all pieces of software used.

        Show
        Myrna van Lunteren added a comment - Interesting, because DERBY-4194 was fixed by regenerating the ui/doc plugin, and it hasn't changed since. I tested the 10.5.3.0 plugin(s) with eclipse galileo 3.5 (& documented it at the time on the testing page: http://wiki.apache.org/db-derby/DerbyTenFiveThreeRelease ). It would help if you could provide a detailed description of all the steps taken, including exact versions & (location of) packages of all pieces of software used.

          People

          • Assignee:
            Myrna van Lunteren
            Reporter:
            Rumen Traykov
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development