Hi, 10.x is on main ;-) Currently, it should mostly be similar to tomee-9.x without the ported Tomcat patching.
Gruß Richard Am 11. August 2023 18:36:58 MESZ schrieb "Benedict Eisenkrämer" <bened...@eisenkramer.de>: >That sounds pretty good to me, seems like an interesting challenge. I have got >some free time next week where I can look into it. > >I just have two smaller questions first: > > * Is this https://github.com/apache/tomee indeed the official > repository for tomee? > * Which branch should I start off on? I would intuitively go for main, > but maybe you have some other branch for 10.x development? > >Best regards, Benedict > > >On 11.08.23 01:05, David Blevins wrote: >> No worries on delays. We're all in the same boat there :) >> >> If you want to dig into this issue a bit, that could be helpful: >> >> -https://issues.apache.org/jira/browse/TOMEE-4166 >> >> Note on expectations; I don't think anyone would be expecting a fully >> functional PR that can run that new TCK setup. Most likely it'd be an >> exercise of reading the TCK setup guide, a bit of poking around code, and a >> series of emails as to what you're finding. With enough discussion we could >> probably all put our heads together on how to actually get it setup and that >> would give the guidance needed to start sending PRs. >> >> How does that sound? >> >> >> -David >> >>> On Aug 2, 2023, at 1:20 PM, Benedict Eisenkrämer<bened...@eisenkramer.de> >>> wrote: >>> >>> Hi David, >>> >>> sorry for my delayed answer I have been pretty busy the last couple of days. >>> >>> To get back to your question, I mostly rely on (specification-wise) JAX-RS, >>> CDI, JPA and Transactions. I might use Websockets and Bean-Validation >>> sometimes. >>> >>> I mostly use the default implementation provided with tomee, except for JPA >>> (Eclipselink isntead of OpenJPA). >>> >>> I have some reasonable experience with these, but mostly from a user side. >>> >>> I hope that answers your question. >>> >>> Best regards, Benedict >>> >>> >>> On 02.08.23 02:23, David Blevins wrote: >>>> Hi Benedict, >>>> >>>> Any thoughts? Definitely don’t want to overload you. >>>> >>>> Happy to find something that fits with how much time you have. >>>> >>>> Thanks again for the interest in helping the project. >>>> >>>> >>>> -David >>>> >>>> >>>>> On Jul 22, 2023, at 2:25 PM, David Blevins<dblev...@tomitribe.com> wrote: >>>>> >>>>> Hi Benedict! >>>>> >>>>> Asking about what you use from a high level as we of course have >>>>> integration code with every specification and there are 30 of them, so >>>>> wanted to point you towards the integration code for a spec you might >>>>> actually use and have some experience in / find relevant to you. >>>>> >>>>> Help passing Jakarta EE compliance tests is definitely helping where it >>>>> counts the most. It’s also the hardest work, but most rewarding. >>>>> >>>>> We should still find a couple small wins so you can get that joy of >>>>> seeing a PR merged, but after that do you use any of these specs? >>>>> >>>>> -https://issues.apache.org/jira/browse/TOMEE-4155 >>>>> >>>>> The Java EE TCK was a huge monolith. Finally in EE 10 some of those TCKs >>>>> have been split out into brand new TCKs. The impact of that is 20 years >>>>> of experience means nothing as each now has all new framework/setup code, >>>>> so we’re all at an equal disadvantage :) >>>>> >>>>> Anyone who takes one of those tasks, including me, is basically going to >>>>> have to learn the TCK setup for each spec and set it up brand new. >>>>> >>>>> >>>>> -David >>>>> >>>>>> On Jul 22, 2023, at 1:59 PM, Benedict >>>>>> Eisenkrämer<bened...@eisenkramer.de> wrote: >>>>>> >>>>>> Hi David, >>>>>> >>>>>> that is actually a pretty good question. If we where speaking about say >>>>>> JPA or CDI I could tell you immediately what features I like the most >>>>>> and what I would improve. >>>>>> With tomee it is quiet different though. It is simply a app-server for >>>>>> me that provides the implementations and runtime for my Java/Jakarta-EE >>>>>> apps. And I think it is very good at that. >>>>>> So I would say I could benefit from anything that brings tomee closer to >>>>>> support newer Versions of JakartaEE. I do not really know what that >>>>>> means on a level of smaller tasks I could contribute though. >>>>>> >>>>>> Best regards, Benedict >>>>>> >>>>>> >>>>>> On 20.07.23 21:06, David Blevins wrote: >>>>>>> Hi Benedict, >>>>>>> >>>>>>> First, thank you for offering your time to the project. This is how >>>>>>> open source should work and rarely does. You already stand out :) >>>>>>> >>>>>>> The most important thing is we work together get you feeling a sense of >>>>>>> being personally invested in the project. Any small contribution that >>>>>>> gets you feeling like you had some impact grows into bigger things over >>>>>>> time. >>>>>>> >>>>>>> So while there are endless things we need, especially given the lack of >>>>>>> resources, we should find some small quick wins that you might find >>>>>>> enjoyable and grow it from there. >>>>>>> >>>>>>> Something that brings you immediate benefit is good. What features of >>>>>>> TomEE do you rely on the most? >>>>>>> >>>>>>> >>>>>>> -David >>>>>>> >>>>>>>> On Jul 18, 2023, at 9:03 AM, Benedict >>>>>>>> Eisenkrämer<bened...@eisenkramer.de> wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I am quite new to this mailing-list so I thought I would introduce >>>>>>>> myself. >>>>>>>> >>>>>>>> My name is Benedict and I am from Germany-Saarland. I work at a local >>>>>>>> software-company as a software-architect and in that role maintain our >>>>>>>> JavaEE, soon to be JakartaEE Framework. >>>>>>>> >>>>>>>> We use tomee as an ApplicationServer for almost a decade now and were >>>>>>>> always happy with it. >>>>>>>> >>>>>>>> >>>>>>>> So to give back a bit I thought I could contribute to the project, >>>>>>>> especially as it seems low on resources at the moment. Unfortunately >>>>>>>> it seems like most of the Information about contributing is rather >>>>>>>> stale. So my question is, what is the best way to contribute to tomee >>>>>>>> at the moment? >>>>>>>> >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Benedict Eisenkrämer >>>>>>>>
