Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.2, 2.0.0
    • Fix Version/s: 1.3.0, 2.0.0
    • Component/s: jpa
    • Labels:
      None

      Issue Links

        Activity

        Donald Woods made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Donald Woods made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Donald Woods made changes -
        Fix Version/s 2.0.0 [ 12314019 ]
        Fix Version/s 2.0.0-M3 [ 12314148 ]
        Donald Woods made changes -
        Fix Version/s 1.3.0 [ 12313326 ]
        Fix Version/s 2.0.0-M3 [ 12314148 ]
        Fix Version/s 2.0.0 [ 12314019 ]
        Donald Woods made changes -
        Link This issue relates to OPENJPA-849 [ OPENJPA-849 ]
        Donald Woods made changes -
        Link This issue is related to OPENJPA-1208 [ OPENJPA-1208 ]
        Hide
        Jeremy Bauer added a comment -

        Sounds good, Tim. I've linked this issue to OPENJPA-773 to keep the compatibility-type items tied together.

        Show
        Jeremy Bauer added a comment - Sounds good, Tim. I've linked this issue to OPENJPA-773 to keep the compatibility-type items tied together.
        Jeremy Bauer made changes -
        Link This issue is related to OPENJPA-773 [ OPENJPA-773 ]
        Hide
        Michael Dick added a comment -

        Actually I'd prefer to just use this issue even if there are only a handful of changes. I think it'll be easier to find later, but I'm fine with either approach. I just saw the empty issue and wasn't sure what to make of it.

        Show
        Michael Dick added a comment - Actually I'd prefer to just use this issue even if there are only a handful of changes. I think it'll be easier to find later, but I'm fine with either approach. I just saw the empty issue and wasn't sure what to make of it.
        Hide
        Tim McConnell added a comment -

        Hi Michael/Jeremy, I now have a good methodology for finding incompatibilities between 2.0 and 1.2.x that is going to take me a couple days to run through and analyze all the scenarios, and attach any pertinent/failing testcases that demonstrates the incompatibility. Once I do that I can better decide whether to handle with this separate umbrella JIRA or not based on the number that I find. My initial analysis is that there are going to be quite numerous so for now I'll keep this JIRA and sub-tasks open. If that does not turn out to be the case, and there are only one or two, I'll move them under OPENJPA-773. That seem reasonable ??

        Show
        Tim McConnell added a comment - Hi Michael/Jeremy, I now have a good methodology for finding incompatibilities between 2.0 and 1.2.x that is going to take me a couple days to run through and analyze all the scenarios, and attach any pertinent/failing testcases that demonstrates the incompatibility. Once I do that I can better decide whether to handle with this separate umbrella JIRA or not based on the number that I find. My initial analysis is that there are going to be quite numerous so for now I'll keep this JIRA and sub-tasks open. If that does not turn out to be the case, and there are only one or two, I'll move them under OPENJPA-773 . That seem reasonable ??
        Hide
        Jeremy Bauer added a comment -

        Thus far, issues have mostly been handled by individual JIRAs (OPENJPA-773 - the 2.0 umbrella JIRA also contains several compatibility issues). There is also a new section in the manual[1] that is describes all the 1.x -> 2.0 migration/compatibility issues. It gets (or should!) get updated as new issues are found/created. We certainly could have a separate umbrella JIRA, but I don't know if is necessary.

        [1] http://openjpa.apache.org/builds/latest/docs/manual/migration_considerations.html

        Show
        Jeremy Bauer added a comment - Thus far, issues have mostly been handled by individual JIRAs ( OPENJPA-773 - the 2.0 umbrella JIRA also contains several compatibility issues). There is also a new section in the manual [1] that is describes all the 1.x -> 2.0 migration/compatibility issues. It gets (or should!) get updated as new issues are found/created. We certainly could have a separate umbrella JIRA, but I don't know if is necessary. [1] http://openjpa.apache.org/builds/latest/docs/manual/migration_considerations.html
        Hide
        Michael Dick added a comment -

        Hi Tim, looks like this is being used as a parent issue for any compatibility changes that we're aware of. Is that the case or will this address a specific issue?

        Show
        Michael Dick added a comment - Hi Tim, looks like this is being used as a parent issue for any compatibility changes that we're aware of. Is that the case or will this address a specific issue?
        Tim McConnell made changes -
        Field Original Value New Value
        Affects Version/s 1.2.2 [ 12313681 ]
        Tim McConnell created issue -

          People

          • Assignee:
            Tim McConnell
            Reporter:
            Tim McConnell
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development