OpenJPA
  1. OpenJPA
  2. OPENJPA-1792

Drop JDK5 support starting with OpenJPA 2.1

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.0
    • Fix Version/s: 2.1.0
    • Component/s: build / infrastructure
    • Labels:
      None

      Description

      There were no -1 votes on the discussion thread to drop JDK5 support from trunk (2.1) so I'll move ahead with it.

        Issue Links

          Activity

          Hide
          Michael Dick added a comment -

          Closing issue which has been resolved for some time. If you believe the issue is not resolved please reopen or open a new issue.

          Show
          Michael Dick added a comment - Closing issue which has been resolved for some time. If you believe the issue is not resolved please reopen or open a new issue.
          Hide
          Ivica Loncar added a comment -

          Sorry for late interruption but as a user of openjpa I object to this decision.

          We can't just force our customers to switch from old runtime environments like WAS 6.1 to new ones like WAS 7.
          This also means we have to run our software on Java 5.

          That said I have to ask: what features are available in JDK 6 and are not available in JDK5?
          I can only think of better apt integration with java compiler.

          Show
          Ivica Loncar added a comment - Sorry for late interruption but as a user of openjpa I object to this decision. We can't just force our customers to switch from old runtime environments like WAS 6.1 to new ones like WAS 7. This also means we have to run our software on Java 5. That said I have to ask: what features are available in JDK 6 and are not available in JDK5? I can only think of better apt integration with java compiler.
          Hide
          Michael Dick added a comment -

          Well, as you said it is a bit late, version 2.1.0 has already been released.

          The 2.0.x branch supports running on JDK5 and there are no plans to remove this support for 2.0.x. Users on JDK5 environments, like WAS 6.1, can continue to use OpenJPA version 2.0.x.

          Show
          Michael Dick added a comment - Well, as you said it is a bit late, version 2.1.0 has already been released. The 2.0.x branch supports running on JDK5 and there are no plans to remove this support for 2.0.x. Users on JDK5 environments, like WAS 6.1, can continue to use OpenJPA version 2.0.x.
          Hide
          Michael Dick added a comment -

          Just an update to my previous comments. The 2.0.x branch is actively maintained and while I don't have a target release date for it, I expect we'll have one in the relatively near future.

          Part of the rationale behind dropping JDK5 support is that we can no longer actively test both environments - especially considering that JDK5 is out of support. For users that still need to run with Java 5, there's the 2.0.x releases. which have nearly the same functionality as 2.1.x. For those that can, or have already moved up there's 2.1.x and beyond.

          Is there something specific from 2.1 that you need in 2.0.x?

          Show
          Michael Dick added a comment - Just an update to my previous comments. The 2.0.x branch is actively maintained and while I don't have a target release date for it, I expect we'll have one in the relatively near future. Part of the rationale behind dropping JDK5 support is that we can no longer actively test both environments - especially considering that JDK5 is out of support. For users that still need to run with Java 5, there's the 2.0.x releases. which have nearly the same functionality as 2.1.x. For those that can, or have already moved up there's 2.1.x and beyond. Is there something specific from 2.1 that you need in 2.0.x?
          Hide
          Ivica Loncar added a comment -

          Michael thanks for clarification.

          We were concerned that patches for bugs wouldn't be regularly backported to 2.0.x.

          Show
          Ivica Loncar added a comment - Michael thanks for clarification. We were concerned that patches for bugs wouldn't be regularly backported to 2.0.x.
          Hide
          Michael Dick added a comment -

          Hi Ivica,

          Having a 2.1.0 release won't affect which changes are ported to 2.0.x. We're generally conservative about what we put into a service release (2.1.x, or 2.0.x) but we're going to maintain both streams. Individual bugs will be evaluated on a case by case basis, but you'll still see fixes going into both streams.

          Show
          Michael Dick added a comment - Hi Ivica, Having a 2.1.0 release won't affect which changes are ported to 2.0.x. We're generally conservative about what we put into a service release (2.1.x, or 2.0.x) but we're going to maintain both streams. Individual bugs will be evaluated on a case by case basis, but you'll still see fixes going into both streams.
          Hide
          Mark Struberg added a comment -

          +1 for dropping the java5 support in 2.2.x. I honestly don't know anyone using it still. They are either still on 1.4.2 or 1.6

          Show
          Mark Struberg added a comment - +1 for dropping the java5 support in 2.2.x. I honestly don't know anyone using it still. They are either still on 1.4.2 or 1.6

            People

            • Assignee:
              Donald Woods
              Reporter:
              Donald Woods
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development