Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: framework-4.0.2
    • Fix Version/s: framework-4.2.0
    • Component/s: Framework, Main
    • Labels:
    • Environment:
      Linux Kubuntu 11.04

      Description

      In Java SE 7 projects I get the following error:
      [WARNING] Signature attribute introduced in version 49.0 class files is ignored in version 48.0 class files
      ...
      [ERROR] COMPILATION ERROR :
      [INFO] -------------------------------------------------------------
      [ERROR] <some class> error: incompatible types
      [ERROR] Object

      I've read about this issue here:
      http://www.mail-archive.com/users@felix.apache.org/msg11574.html

      and here:
      http://stackoverflow.com/questions/4058661/java-compilers-target-version-jsr14-with-jdk7-8

      The according JDK bug report has been closed as "Not a Defect": http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7078419

      So this has to be fixed on Apache Felix side.

      Please deploy a version to Maven Central which works with Java SE 7.

        Issue Links

          Activity

          Hide
          rickhall Richard S. Hall added a comment -

          I'm fine if we switch the framework to target Java 5 by default rather than jsr14, which should solve the issue, but that will have to wait for the next release.

          Show
          rickhall Richard S. Hall added a comment - I'm fine if we switch the framework to target Java 5 by default rather than jsr14, which should solve the issue, but that will have to wait for the next release.
          Hide
          puce Florian Brunner added a comment -

          OK, great. Any timeline for this? There's not much information on the roadmap page: https://felix.apache.org/site/roadmap.html

          Show
          puce Florian Brunner added a comment - OK, great. Any timeline for this? There's not much information on the roadmap page: https://felix.apache.org/site/roadmap.html
          Hide
          rickhall Richard S. Hall added a comment -

          Not really. Until then, just recompile it yourself.

          Show
          rickhall Richard S. Hall added a comment - Not really. Until then, just recompile it yourself.
          Hide
          rickhall Richard S. Hall added a comment -

          Updated framework and main pom files to target 1.5.

          Show
          rickhall Richard S. Hall added a comment - Updated framework and main pom files to target 1.5.
          Hide
          puce Florian Brunner added a comment -

          I'm still getting the same issue with framework-4.0.3

          Show
          puce Florian Brunner added a comment - I'm still getting the same issue with framework-4.0.3
          Hide
          rickhall Richard S. Hall added a comment -

          Notice the "fix version" on this issue, it is framework 4.2.0 not 4.0.3...i.e., it hasn't been released yet. If you want to try it out you need to build from trunk or use the latest snapshot. Thanks.

          Show
          rickhall Richard S. Hall added a comment - Notice the "fix version" on this issue, it is framework 4.2.0 not 4.0.3...i.e., it hasn't been released yet. If you want to try it out you need to build from trunk or use the latest snapshot. Thanks.

            People

            • Assignee:
              rickhall Richard S. Hall
              Reporter:
              puce Florian Brunner
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development