I have tested a custom TomEE 10 build (with fixed deps) for quite a while now and it worked for my usecases.
What needs to be done (imho): - We need to have stable versions for BatchEE and OpenJPA. Currently, they are only SNAPSHOT. - Implement the concurrency changes. Currently, they are only added as stub impls. (I am not using that in my test env, so didn't encounter issues) - TCK still hangs but isn't a blocker for a milestone imho. Thoughts? Gruß Richard Am 5. Januar 2024 10:40:05 MEZ schrieb Thomas Andraschko <andraschko.tho...@gmail.com>: >i would like to have everything apache, too but i think our goal must be to >get a TomEE10-M1 release out ASAP. >we can later easily make openjpa the default again. > >how should we proceed here? >i have some time slots to work on something and provide PRs, we just need >some decisions. > > >Am Mo., 20. Nov. 2023 um 23:12 Uhr schrieb Jonathan S. Fisher < >exabr...@gmail.com>: > >> If my opinion counts for anything, I'd love for TomEE to be based on >> Apache Foundation projects as much as possible. With JPA itself is >> just a large spec to cover, I can understand OpenJPA not having a >> current spec implementation and am still thankful for the past efforts >> of the committers on that project. My second choice would be >> EclipseLink over Hibernate, mainly because of speed, but also because >> many of the app servers in the space are already Weld + Hibernate + >> other various Redhat derivative projects. TomEE by far is enormously >> faster on startup and execution speed than OpenLiberty or WildFly >> (deploying the exact same WAR) and I'd be sad to lose that. >> >> >> On Mon, Nov 20, 2023 at 9:46 AM Jean-Louis Monteiro >> <jlmonte...@tomitribe.com> wrote: >> > >> > Thanks Thomas for pointing this out. >> > -- >> > Jean-Louis Monteiro >> > http://twitter.com/jlouismonteiro >> > http://www.tomitribe.com >> > >> > >> > On Mon, Nov 20, 2023 at 4:06 PM Richard Zowalla <r...@apache.org> wrote: >> > >> > > Great news ;-) >> > > >> > > Am Montag, dem 20.11.2023 um 16:05 +0100 schrieb Thomas Andraschko: >> > > > JFYI: https://in.relation.to/2023/11/18/license/ >> > > > >> > > > it seems they would like to move to another license >> > > > >> > > > Am Di., 7. Feb. 2023 um 16:16 Uhr schrieb Jean-Louis Monteiro < >> > > > jlmonte...@tomitribe.com>: >> > > > >> > > > > https://hibernate.org/community/license/ >> > > > > >> > > > > Most Hibernate projects are released under LGPL v2.1 >> > > > > <https://opensource.org/licenses/LGPL-2.1>. >> > > > > Only some sub projects are ASL v2 >> > > > > -- >> > > > > Jean-Louis Monteiro >> > > > > http://twitter.com/jlouismonteiro >> > > > > http://www.tomitribe.com >> > > > > >> > > > > >> > > > > On Tue, Feb 7, 2023 at 4:12 PM Thomas Andraschko < >> > > > > andraschko.tho...@gmail.com> wrote: >> > > > > >> > > > > > isnt hibernate licensed under Apache2.0? >> > > > > > >> > > > > > Am Di., 7. Feb. 2023 um 16:10 Uhr schrieb Swell < >> > > > > souheil.sul...@gmail.com >> > > > > > > : >> > > > > > >> > > > > > > Because of licenses we cannot ship with hibernate. Better be >> > > > > éclipselink >> > > > > > to >> > > > > > > avoid license hell. >> > > > > > > >> > > > > > > On Tue 7 Feb 2023 at 16:08, Thomas Andraschko < >> > > > > > andraschko.tho...@gmail.com >> > > > > > > > >> > > > > > > wrote: >> > > > > > > >> > > > > > > > Hi, >> > > > > > > > >> > > > > > > > AFAICS OpenJPA isnt in real active development and doenst >> > > > > > > > even >> > > > > support >> > > > > > > all >> > > > > > > > JPA 2.2 features. >> > > > > > > > Whats your plan for it? >> > > > > > > > Can't we just use Hibernate as default? >> > > > > > > > >> > > > > > > > Best regards, >> > > > > > > > Thomas >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > >> > > >> >> >> >> -- >> Jonathan | exabr...@gmail.com >> Pessimists, see a jar as half empty. Optimists, in contrast, see it as >> half full. >> Engineers, of course, understand the glass is twice as big as it needs to >> be. >>
