Menu

JEdit plugin install error: Major.minor version not supported

Help
David Le
2016-04-11
2016-04-12
  • David Le

    David Le - 2016-04-11

    Hi,

    I have tried to install JEdit's CZT pluggin as instructed on the web site. However, on restarting jEdit after installing the plug-in jars and before the "Installing the Z modes" step, the following error occured:

    <home-dir-path>/.jedit/jars/ZCharMap.jar:
    Cannot start: java.lang.UnsupportedClassVersionError: net/sourceforge/czt/jedit/zcharmap/CommunityZToolsPlugin : Unsupported major.minor version 52.0
    Try updating to a newer version of the plugin.

    From experience with Java, this error occurs b/c of the compatibility between jEdit's Java and the class files contained in the mentioned plugin jar.

    I am using the latest jEdit which is installed from my xubuntu repository (version 5.1).

    Please advice.

    Thank you very much for your help.

     
    • Leo Freitas

      Leo Freitas - 2016-04-11

      Hi

      jEdit was used as a first IDE to play with integrating CZT with. Work on that stopped a only time ago.
      With local expertise on Eclipse, we went on to develop the plugins for Eclipse for Z and Z/Eves.

      So most likely there is now some incompatibility between jEdit and what we did. So I am afraid for OZ, there is just the command line them.
      A suggestion would be to try and recompile the sources using one of the solutions given here:

      http://stackoverflow.com/questions/22489398/unsupported-major-minor-version-52-0

      Try that and see/tell us what happens.

      Best,
      Leo

      On 11 Apr 2016, at 03:15, David Le dmle@users.sf.net wrote:

      Hi,

      I have tried to install JEdit's CZT pluggin as instructed on the web site. However, on restarting jEdit after installing the plug-in jars and before the "Installing the Z modes" step, the following error occured:

      <home-dir-path>/.jedit/jars/ZCharMap.jar:
      Cannot start: java.lang.UnsupportedClassVersionError: net/sourceforge/czt/jedit/zcharmap/CommunityZToolsPlugin : Unsupported major.minor version 52.0
      Try updating to a newer version of the plugin.

      From experience with Java, this error occurs b/c of the compatibility between jEdit's Java and the class files contained in the mentioned plugin jar.

      I am using the latest jEdit which is installed from my xubuntu repository (version 5.1).

      Please advice.

      Thank you very much for your help.

      JEdit plugin install error: Major.minor version not supported https://sourceforge.net/p/czt/discussion/295268/thread/d1a4f23e/?limit=25#8e3d
      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/czt/discussion/295268/ https://sourceforge.net/p/czt/discussion/295268/
      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ https://sourceforge.net/auth/subscriptions/

       
  • Andrius Velykis

    Andrius Velykis - 2016-04-11

    Hi David,

    Which version of Java are you using? Can you try using Java 8 and see if it helps? I think since it was announced mid last year that Java 7 was stopping public updates, we switched to Java 8 for building (as it is time consuming to maintain multiple versions).

    Andrius

     
    • David Le

      David Le - 2016-04-11

      Hi Andrius and Leo,

      Thank you for your prompt response.

      I have just had a chance to look more into this problem and found that it is true that jEdit is running on my default current jdk (1.7), while the plug-ins were compiled using version 1.8. I switched to using 1.8 to run jEdit and it worked ok.

      I have just been able to open my OZ specification file in jEdit with syntax highlighting. It is better than with the current CZT Eclipse IDE b/c the IDE currently does not support syntax highlighting for this dialect (as correctly suggested by Leo in my early conversations with him)

      For now, I will be editing my specification in jEdit and type-checking it using the command line (java -jar czt.jar ozedtypecheck).

      By the way, may I ask how can I latex-compile my specification file? This morning I tried it by copying the czt.sty and all the .tex files from the czt.jar/lib directory to the directory of my spec file and run latex on this file. But i got the following error (UMLType is a class that I defined in the spec):

      <<<
      ! LaTeX Error: Environment class undefined.

      See the LaTeX manual or LaTeX Companion for explanation.
      Type H <return> for immediate help.
      ...

      l.42 \begin{class}
      {UMLType}
      ?

      Thanks very much

       
      • Leo Freitas

        Leo Freitas - 2016-04-12

        Hi David,

        I am glad you managed to get it running. For LaTeX typesetting, you’ve got another problem, with the same/similar kind of answer: most development in recent years took place for Z and Z/Eves.

        The OZ LaTeX package is oz.sty, which I just realised is not in the repository, but is instead on TUG

        https://www.ctan.org/tex-archive/macros/latex/contrib/objectz?lang=en

        This is something we should do as well (i.e. put czt.sty into TUG), but haven’t. When I extended/consolidated czt.sty I was taking into account various versions of LaTeX (2.09, 2e), Z (Standard, Spivey, Z/Eves) and Unicode (ISO-Z was prior to unicode standard). This took a while, and led to czt.sty. I don’t think there was ever a development for a cztoz.sty.

        That is, the of-the-shelf oz.sty might not work directly with OZ files, but it is worth a try.

        I guess the overall message is that front-end support for other dialects is pretty much up to the user. Only the parser/typechecker/AST for programming and surrounding context (i.e. theory loading/section management) is thoroughly available for all dialects and is well tested/developed. IDEs, LaTeX, fonts, etc, needs work.

        Best,
        Leo

        On 11 Apr 2016, at 14:16, David Le dmle@users.sf.net wrote:

        Hi Andrius and Leo,

        Thank you for your prompt response.

        I have just had a chance to look more into this problem and found that it is true that jEdit is running on my default current jdk (1.7), while the plug-ins were compiled using version 1.8. I switched to using 1.8 to run jEdit and it worked ok.

        I have just been able to open my OZ specification file in jEdit with syntax highlighting. It is better than with the current CZT Eclipse IDE b/c the IDE currently does not support syntax highlighting for this dialect (as correctly suggested by Leo in my early conversations with him)

        For now, I will be editing my specification in jEdit and type-checking it using the command line (java -jar czt.jar ozedtypecheck).

        By the way, may I ask how can I latex-compile my specification file? This morning I tried it by copying the czt.sty and all the .tex files from the czt.jar/lib directory to the directory of my spec file and run latex on this file. But i got the following error (UMLType is a class that I defined in the spec):

        <<<
        ! LaTeX Error: Environment class undefined.

        See the LaTeX manual or LaTeX Companion for explanation.
        Type H <return> for immediate help.
        ...
        l.42 \begin{class}
        {UMLType}
        ?

        Thanks very much

        JEdit plugin install error: Major.minor version not supported https://sourceforge.net/p/czt/discussion/295268/thread/d1a4f23e/?limit=25#60c8/43d0
        Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/czt/discussion/295268/ https://sourceforge.net/p/czt/discussion/295268/
        To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ https://sourceforge.net/auth/subscriptions/

         
        • David Le

          David Le - 2016-04-12

          Hi Leo,

          Thank you so much.

          I will download the oz.sty and try it. Hope it works.

           
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.