Ok, so the draft text should be something like as following:
OpenJPA 3.0.0: compatibility set for JPA 2.1; implements: stored
procedures, DDL generation (would make sense to include what's missing?
is the "what's new" list on [1] reliable?)
OpenJPA 3.0.1: compatibility set for JPA 2.2, currently preparing code
for JakartaEE JPA TCK tests; implements: stream query results (would
make sense to include what's missing? is the "what's new" list on [2]
reliable?)
I think that, besides what is mentioned in OPENJPA-2765, [3] should be
updated or renamed as [4], with consistent text modification.
Regards.
[1] https://en.wikibooks.org/wiki/Java_Persistence/What_is_new_in_JPA_2.1%3F
[2] https://thoughts-on-java.org/whats-new-in-jpa-2-2/
[3] http://openjpa.apache.org/jpa-2.1-development-process.html
[4]http://openjpa.apache.org/jpa-2.2-development-process.html
On 09/01/19 08:25, Romain Manni-Bucau wrote:
Hmm, wasnt it done in two previous answers?
Le mer. 9 janv. 2019 08:06, Francesco Chicchiriccò <ilgro...@apache.org> a
écrit :
Hi all,
sorry to bother, but I think we should fix the communication anytime
soon: I understand that Mark's statement below means that we will be
soon able to report exactly what's the compatibility status of
3.0.1-SNAPSHOT, but what about 3.0.0? I know it depends on JPA 2.1
specs, but can someone briefly highlight what is missing (and / or what
is implemented)?
Regards.
On 07/01/19 12:02, Mark Struberg wrote:
I've gradually improved our test coverage and internal code parts by
adding docker profiles for multiple Databases over the last months.
I did add Oracle11_XE yesterday. Although the setup is not yet perfect
we can at least run the tests now.
So basically everyone can now test against a bunch of different
databases.
The next step will be to include the JakartaEE JPA TCK.
And then we will know exactly what's missing.
LieGrue,
strub
Am 07.01.2019 um 11:47 schrieb Francesco Chicchiriccò <
ilgro...@apache.org>:
On 07/01/19 11:45, Romain Manni-Bucau wrote:
Hi Francesco,
I will not have much time these days to help very actively but i'd
expose
it the other way around, more roadmap oriented:
OpenJPA 3.0.0: provides stored procedure support of JPA 2.1 etc...
cause structurally we are more about adding features one by one than
saying
"we just miss X and Y" for now - which is fine IMHO but just trying to
explain why we must not reference ourself to JPA 2.2 completeness but
more
on a kind of timeline.
I understand, that's fine; I would still need to fill up the statements
above for both 3.0.0 and 3.0.1: would you be able to provide those?
Regards.
Le lun. 7 janv. 2019 à 11:43, Francesco Chicchiriccò <
ilgro...@apache.org>
a écrit :
Hi all,
a recent conversation on Twitter [1] with Oliver Drotbohm, Spring Data
project lead, highlighted the need to clarify what is the JPA spec
level
implemented by the various OpenJPA releases; for such a purpose, [2]
was
opened.
I personally believe it is quite important to timely react, and I also
offer my availability to align the various docs, if no one else steps
in; for such a purpose, however, I would really appreciate some kind
of
draft statements like as follows:
* OpenJPA 2.x - fully implements JPA 2.0 specs, pass JPA TCK
* OpenJPA 3.0.0 - depends on JPA 2.1 specs, JPA TCK not available at
release time - missing JPA 2.1 features: A,B,C...
* OpenJPA 3.0.1 - not released yet, depends on JPA 2.2 specs, JPA TCK
compliance not yet verified - missing JPA 2.2 features: D,E,F...
WDYT?
Regards.
[1] https://twitter.com/odrotbohm/status/1081713555290972160
[2] https://issues.apache.org/jira/browse/OPENJPA-2765
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
