Re: [VOTE] Apache XBean 4.25 release

+1 txs and LieGrue, strub > Am 15.04.2024 um 13:34 schrieb fpapon : > > Hi everyone, > > I submit Apache XBean 4.25 release to your vote. > > This release mainly includes (other issue description is available on > the release note): > > * Bug > - [XBEAN-343] - consistent handling of

Re: Arthur release

all fine, go on! txs and LieGrue, strub > Am 05.04.2024 um 09:30 schrieb Francois Papon : > > Hi all, > > I would like to start the release process for Arthur, any objection? > > regards, > > François >

Status BatchEE-2.0.0

Hi folks! I've now finished the work on BatchEE-2.0.0. I think we have to enable the TCK still, but all our internal tests do work again. Note that I had to move back to an old Camel version due to getting test errors with a newer version. Would be great if someone could please take a look at

Re: [VOTE] [RESULT] Release Apache Geronimo BatchEE-1.0.3

Hi! And here comes my own +1 That makes it: +1: Romain, Francois, Jean-Louis, Mark No -1 nor 0 I'll go on to publish the repo etc. LieGrue, strub > Am 18.04.2023 um 12:26 schrieb Mark Struberg : > > Hi! > > I'd like to call a VOTE on releasing BatchEE-1.0.3. > > This is mostly an

Re: [VOTE] Release Apache Geronimo BatchEE-1.0.3

n.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > Le mar. 18 avr. 2023 à 12:27, Mark Struberg via dev <mailto:dev@geronimo.apache.org>> a écrit : >> Hi! >> >> I'd lik

[VOTE] Release Apache Geronimo BatchEE-1.0.3

Hi! I'd like to call a VOTE on releasing BatchEE-1.0.3. This is mostly an update to the latest TomEE version and a fix in the ChildFirstURLClassLoader [BATCHEE-162 ] - improve reproducible builds [BATCHEE-167

Re: [VOTE] Release Geronimo Arthur 1.0.6

+1 LieGrue, strub > Am 17.04.2023 um 20:54 schrieb fpapon : > > Hi, > > This is a call to vote in favor of releasing Apache Geronimo Arthur version > 1.0.6. > > We solved 7 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10220=12351343 > > ** Bug > *

Re: [batchee] future?

anager, batchEE, etc). So they need a home. Of course we can >> split them apart and give them to different projects, but it does not solve >> any problem. The people are the same. As soon as we allow all projects to >> contribute or even become committers here, I don't see any issue

Re: [CDI40] how to tackle the jakarta 10 APIs?

far as I've looked through a bunch of spec api jars. LieGrue, strub > Am 23.11.2022 um 11:02 schrieb Romain Manni-Bucau : > > > > > Le mer. 23 nov. 2022 à 10:58, Mark Struberg via dev <mailto:dev@geronimo.apache.org>> a écrit : >> As written over at the

Re: [CDI40] how to tackle the jakarta 10 APIs?

/> | Old Blog > <http://rmannibucau.wordpress.com/> | Github <https://github.com/rmannibucau> > | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > Le mar. 22 nov

Re: [batchee] future?

ent, just making it living (updating versions and spec impl). >> >> Le mar. 22 nov. 2022 à 23:31, Mark Struberg via dev > <mailto:dev@geronimo.apache.org>> a écrit : >>> I still use batchee very much. So I'd keep it well alive. Also investing >>> time on a

[CDI40] how to tackle the jakarta 10 APIs?

Hi! How do we want to approach the CDI-4.0 api? I don't want to just use the official API as it is bloated with the 'CDI light' stuff. So there is good reason to just keep our own version - even if it is just a shaded/spit of the official one. What about the others? Do we still want to roll

Re: [batchee] future?

I still use batchee very much. So I'd keep it well alive. Also investing time on and on. Is there anything which is required to do? LieGrue, strub > Am 18.11.2022 um 09:50 schrieb Francois Papon : > > Hi, > > I don't have insights about how BatchEE is used today and how the jbatch >