openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-404) Backward-compatibility for pre-1.0 APIs
Date Wed, 24 Oct 2007 13:06:52 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537316
] 

Kevin Sutter commented on OPENJPA-404:
--------------------------------------

FWIW, WebSphere's compatibility policy seems to be in synch with BEA's -- two major release
cycle.  We also understand that attempting to keep OpenJPA in synch with WebSphere's release
cycles will be a challenge.  But, as long as we (OpenJPA) are consistent with our release
and compatibility strategy, then we should be able to meld with any other app server's release
cycle (in one form or another).

Kevin

> Backward-compatibility for pre-1.0 APIs
> ---------------------------------------
>
>                 Key: OPENJPA-404
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-404
>             Project: OpenJPA
>          Issue Type: New Feature
>    Affects Versions: 1.0.0
>            Reporter: Patrick Linskey
>             Fix For: 1.1.0
>
>         Attachments: OPENJPA-404.patch
>
>
> When I changed the OpenJPA APIs before the 1.0 release, I made a number of incompatible
changes. At the time, we deemed that this was fine since 1.0 was the first OpenJPA release.
However, it turns out that this runs up against BEA policy, since BEA shipped a product using
a build from around 0.9.7. So, we'd like to do some work to address this where possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message