Re: [batchee] future?

[Raymond Augé]

ache.org> a écrit :
>>>>>
>>>>>> 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 <
>>>>>> francois.pa...@openobject.fr>:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I don't have insights about how BatchEE is used today and how the
>>>>>> jbatch specification is support by others.
>>>>>>
>>>>>> +1 for freeze.
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> François
>>>>>> On 18/11/2022 08:21, Romain Manni-Bucau wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> We discussed some time ago to drop batchee as an active subproject,
>>>>>> wonder where we are now on this?
>>>>>> Do we freeze it and document we don't maintain it anymore?
>>>>>>
>>>>>> Romain Manni-Bucau
>>>>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>>>>>> <https://rmannibucau.metawerx.net/> | 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>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> Jean-Louis
>>>>
>>>>
>>>>
>>>
>>> --
>>> Jean-Louis
>>>
>>

-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Re: Proposal: Retiring the Geronimo Project

[Raymond Augé]

Thanks for your feedback Romain, but if you read carefully what I wrote, I
exactly suggested doing the adoption process before doing any retirement.

I'm glad you agree with that part.

Ray

On Mon, Jul 11, 2022 at 1:00 PM Romain Manni-Bucau 
wrote:

> Hi Raymond,
>
> Guess before retiring we should find a home for all residents (Geronimo by
> itself is not dead and we have several subprojects which should stay
> somewhere) so -1 as of today even if I agree with most of what you said and
> the high level idea behind.
>
> My blind guess is that we should at least await october for such a work
> since it will be summer holidays then september rush but we should probably
> plan to tackle that topic at that time - can be a board report point
> thinking out loud.
>
> Hope it makes sense.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | 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 lun. 11 juil. 2022 à 18:52, Raymond Augé  a
> écrit :
>
>> The "Geronimo" project is getting long in the tooth and has very few
>> maintainers. It's been teetering on the edge of what could be considered
>> active ever since I've been involved (I believe more than 5 years now.)
>>
>> The project has seen many parts of its portfolio go unmaintained or
>> deprecated. We've seen other projects adopt parts (with this project's
>> blessing [1]). I would also argue this project seems to have lost its
>> identity and is now some sort of mishmash of libraries and utilities with
>> barely related aspects which I don't believe is really the model for a good
>> Open Source Apache project to bank a future on.
>>
>> And now, we really should make an effort to settle the issue of
>> "Native"-themed mascotry which was raised again most recently here [2].
>>
>> PROPOSAL:
>> I would like to propose we attempt to find any other ASF projects that
>> would be willing to take over interesting parts of the portfolio. After
>> that is exhausted, if nothing significant of interest remains the project
>> could simply be retired. However, if something significant does remain and
>> someone speaks up about wanting to maintain it, they could initiate a new
>> ASF project to house the remaining parts and have the new project adopt
>> those interesting bits.
>>
>> Thoughts?
>>
>> Ray
>>
>> [1] https://lists.apache.org/thread/sdny91l920o2lnl58sj5wy577k39fhsz
>> [2] https://lists.apache.org/thread/bd8s3knj2541275rbdnx2718h0y8qhrj
>>
>>

-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Proposal: Retiring the Geronimo Project

[Raymond Augé]

The "Geronimo" project is getting long in the tooth and has very few
maintainers. It's been teetering on the edge of what could be considered
active ever since I've been involved (I believe more than 5 years now.)

The project has seen many parts of its portfolio go unmaintained or
deprecated. We've seen other projects adopt parts (with this project's
blessing [1]). I would also argue this project seems to have lost its
identity and is now some sort of mishmash of libraries and utilities with
barely related aspects which I don't believe is really the model for a good
Open Source Apache project to bank a future on.

And now, we really should make an effort to settle the issue of
"Native"-themed mascotry which was raised again most recently here [2].

PROPOSAL:
I would like to propose we attempt to find any other ASF projects that
would be willing to take over interesting parts of the portfolio. After
that is exhausted, if nothing significant of interest remains the project
could simply be retired. However, if something significant does remain and
someone speaks up about wanting to maintain it, they could initiate a new
ASF project to house the remaining parts and have the new project adopt
those interesting bits.

Thoughts?

Ray

[1] https://lists.apache.org/thread/sdny91l920o2lnl58sj5wy577k39fhsz
[2] https://lists.apache.org/thread/bd8s3knj2541275rbdnx2718h0y8qhrj

Re: Moving Mail, Activation, Transaction and Connector to Apache TomEE (was Re: [DISCUSS] Move microprofile impl to Apache TomEE)

[Raymond Augé]

FYI here's my +1 w.r.t. the move.

Best of luck

On Thu, Jul 7, 2022 at 5:08 AM Romain Manni-Bucau 
wrote:

> If it helps: the package is not a big deal for javax -> jakarta concerned
> bundles but can be for the one already migrated. A note is that the OSGi
> compliance should probable be kept inside tomee project since several
> consumers are OSGi ones but nothing crazy or not already done @tomee AFAIK.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | 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 jeu. 7 juil. 2022 à 10:19, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> a écrit :
>
>> Hi all,
>>
>> to summarize the current discussion:
>>
>> From the discussion, it looks like, that there are no real objections /
>> blockers for a move?
>>
>> However, a move of the packages / project might confuse users and
>> automated tools (like dependency update check tooling). We would need
>> to communicate / announce it accordingly, but haven't discussed this
>> aspect much atm?
>>
>> It seems, that an open task is to complete the move from svn to git for
>> the repositories where it isn't already done. Guess, this should happen
>> first...
>>
>> Gruß
>> Richard
>>
>>
>> Am Dienstag, dem 14.06.2022 um 22:09 -0700 schrieb David Jencks:
>> > I think each impl. needs to be in its own git repo, I’m not sure
>> > which already are.
>> >
>> > I believe the tx manager is used in an OSGI spec impl in (I think)
>> > Aries. On the other hand they might have copied the implementation.
>> >  It might be confusing if the governing project and/or package names
>> > change. I don’t know if there are other uses, or how to find out.
>> >
>> > It might possibly be simpler, after we get each subproject into
>> > appropriate git repos, to make people who want to work on these
>> > implementations geronimo committers.
>> >
>> > David Jencks
>> >
>> > > On Jun 14, 2022, at 9:36 AM, Romain Manni-Bucau <
>> > > rmannibu...@gmail.com> wrote:
>> > >
>> > > No blocker from me (minor note being some are already on git so
>> > > don't start back from svn ;))
>> > >
>> > > Romain Manni-Bucau
>> > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
>> > >
>> > >
>> > > Le mar. 14 juin 2022 à 18:29, David Blevins <
>> > > david.blev...@gmail.com> a écrit :
>> > > > Jumping off of this thread, is there any openness to discussing
>> > > > moving this code over to TomEE?
>> > > >
>> > > >  -
>> > > >
>> http://svn.apache.org/repos/asf/geronimo/components/txmanager/trunk/
>> > > >  -
>> > > >
>> http://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-activation_2.0_spec/
>> > > >  -
>> > > >
>> http://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jakartamail_2.1_spec/
>> > > >  -
>> > > >
>> http://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-mail_2.1_spec/
>> > > >
>> > > > These are on the critical path for TomEE, being updated in
>> > > > Jakarta EE 10.  We're not working on Jakarta EE 10 yet, but we'll
>> > > > hopefully be doing that by early next year.
>> > > >
>> > > > It's a bit painful to send people over from the TomEE project to
>> > > > here and submit patches against SVN repos.  It would be great if
>> > > > we could have them in git and under the TomEE PMC if possible.
>> > > >
>> > > > Thoughts?
>> > > >
>> > > >
>> > > > -David
>> > > >
>> > > > > On Jun 6, 2022, at 1:59 AM, fpapon  wrote:
>> > > > >
>> > > > > Hi all,
>> > > > >
>> > > > > I would like to start a thread to discuss about the future of
>> > > > the Apache Geronimo Microprofile implementation:
>> > > > >
>> > > > > https://geronimo.apache.org/microprofile/
>> > > > >
>> > > > > As we can see, we don't have a lot of traction about the
>> > > > maintenance of the implementation to be up-to-date with the
>> > > > Microprofile specification.
>> > > > >
>> > > > > The J2EE Geronimo server is no longer exist and at Apache, the
>> > > > active EE server seems to be Apache TomEE.
>> > > > >
>> > > > > May be it could make more sense to move the Microprofile
>> > > > implementation to the Apache TomEE umbrella.
>> > > > >
>> > > > > WDYT?
>> > > > >
>> > > > > regards,
>> > > > >
>> > > > > --
>> > > > > --
>> > > > > François
>> > > > >
>> > > >
>> >
>> >
>>
>

-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Re: Apache Geronimo Mail (provider) 2.1 - 1.0.0

[Raymond Augé]

+1 (binding)

On Mon, Jun 20, 2022 at 11:14 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Hi,
>
> I'd like to call a vote for Apache Geronimo Mail 2.1 version 1.0.0. This
> is the first implementation of the Jakarta based Mail 2.1 specification. It
> does not fully pass the standalone TCK but the mail part of the platform
> TCK already passes.
>
> *Sources*
>
> https://dist.apache.org/repos/dist/dev/geronimo/javamail/geronimo-mail_2.1_mail-1.0.0/
>
> *Github Tag*
> https://github.com/apache/geronimo-javamail/tree/geronimo-mail_2.1-1.0.0
>
> *Staging repo*
> https://repository.apache.org/content/repositories/orgapachegeronimo-1156
>
> *Release notes*
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10220=12351860
>
> New Feature
>
>- [GERONIMO-6837 <https://issues.apache.org/jira/browse/GERONIMO-6837>]
>- Implement Geronimo Mail 2.1 for Jakarta Mail 2.1
>
> Improvement
>
>- [GERONIMO-6838 <https://issues.apache.org/jira/browse/GERONIMO-6838>]
>- Support additional body after IMAP CONTINUATION response
>- [GERONIMO-6839 <https://issues.apache.org/jira/browse/GERONIMO-6839>]
>- Upgrade to Activation Spec 2.0 - 1.0.0-M1
>
>
> [ ] +1 approve this release
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> Here is my +1 Binding vote.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Re: [VOTE] Geronimo activation_2.0_spec 1.0.0

[Raymond Augé]

f
>>>>>> > >
>>>>>> https://jakarta.ee/specifications/activation/2.0/jakarta-activation-spec-2.0.html
>>>>>> > >  doesn't mention anything about it.
>>>>>> > >
>>>>>> > > Guess it is a relict from java.awt.DataFlavour (also @Deprecated
>>>>>> > > there)
>>>>>> > > to keep compatibility after removing the references to it.
>>>>>> > >
>>>>>> > > Am Dienstag, dem 24.05.2022 um 12:42 +0200 schrieb Romain Manni-
>>>>>> > > Bucau:
>>>>>> > > > Hmm, before that the question is "are the TCK spec compliant", a
>>>>>> > > lot
>>>>>> > > > have a reference in the spec we maybe missed, do you have some
>>>>>> > > > pointers on them? If we were wrong let's fix it, if the TCK are
>>>>>> > > wrong
>>>>>> > > > then maybe ignore the TCK?
>>>>>> > > >
>>>>>> > > > Romain Manni-Bucau
>>>>>> > > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
>>>>>> > > >
>>>>>> > > >
>>>>>> > > > Le mar. 24 mai 2022 à 12:33, Zowalla, Richard <
>>>>>> > > > richard.zowa...@hs-heilbronn.de> a écrit :
>>>>>> > > > > There is a TCK test regarding normalizeMimeTypeParameter which
>>>>>> > > > > broke with the current impl of normalizeMimeTypeParameter
>>>>>> > > > >
>>>>>> > > > > Therefore, I adjusted it but agree that it is mit really
>>>>>> > > specified.
>>>>>> > > > > Question would be, if it is "ok" to fail specific tests of the
>>>>>> > > TCK.
>>>>>> > > > >
>>>>>> > > > > Gruß
>>>>>> > > > > Richard
>>>>>> > > > > Von: Romain Manni-Bucau 
>>>>>> > > > > Gesendet: Dienstag, 24. Mai 2022 11:53:37
>>>>>> > > > > An: dev@geronimo.apache.org
>>>>>> > > > > Betreff: Re: [VOTE] Geronimo activation_2.0_spec 1.0.0
>>>>>> > > > >
>>>>>> > > > > Not voting negatively but seems we
>>>>>> > > > > broke normalizeMimeTypeParameter (I guess copying the RI?) and
>>>>>> > > I'm
>>>>>> > > > > not sure it should be done.
>>>>>> > > > > From my understanding this part is not well specified and
>>>>>> > > highly
>>>>>> > > > > depends on the impl but I don't see a reson to break existing
>>>>>> > > > > consumers which I always favor in regards of being aligned on
>>>>>> > > the
>>>>>> > > > > RI.
>>>>>> > > > >
>>>>>> > > > > Romain Manni-Bucau
>>>>>> > > > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
>>>>>> > > > >
>>>>>> > > > >
>>>>>> > > > > Le mar. 24 mai 2022 à 11:45, Jean-Louis Monteiro <
>>>>>> > > > > jlmonte...@tomitribe.com> a écrit :
>>>>>> > > > > > Here we go
>>>>>> > > > > >
>>>>>> > > > > > We now pass all TCK and signature tests. Thanks Richard.
>>>>>> > > > > >
>>>>>> > > > > > This is essentially the same as the M1 David did last week
>>>>>> > > but
>>>>>> > > > > > with the fixes for compliance (See GERONIMO-6832)
>>>>>> > > > > >
>>>>>> > > > > > Here is the link for sources
>>>>>> > > > > >
>>>>>> > >
>>>>>> https://dist.apache.org/repos/dist/dev/geronimo/activation_2.0_spec/
>>>>>> > > > > >
>>>>>> > > > > > Here is the svn tag
>>>>>> > > > > >
>>>>>> > >
>>>>>> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-activation_2.0_spec-1.0.0/
>>>>>> > > > > >
>>>>>> > > > > > Here is the staging repo
>>>>>> > > > > >
>>>>>> > >
>>>>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1155
>>>>>> > > > > >
>>>>>> > > > > > Please vote to approve this release:
>>>>>> > > > > > [ ] +1 Approve the release
>>>>>> > > > > > [ ]  0 Abstain (please provide specific comments)
>>>>>> > > > > > [ ] -1 Don't approve the release (please provide specific
>>>>>> > > > > > comments)
>>>>>> > > > > >
>>>>>> > > > > > This vote will be open for at least 72 hours.
>>>>>> > > > > >
>>>>>> > > > > > Thanks
>>>>>> > > > > >
>>>>>> > > > > >
>>>>>> > > > > >
>>>>>> > > > > > --
>>>>>> > > > > > Jean-Louis Monteiro
>>>>>> > > > > > http://twitter.com/jlouismonteiro
>>>>>> > > > > > http://www.tomitribe.com
>>>>>> > > > > >
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jean-Louis
>>>>>
>>>>
>>>>
>>>> --
>>>> Jean-Louis
>>>>
>>>
>>
>> --
>> Jean-Louis
>>
>
>
> --
> Jean-Louis
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Re: [DISCUSS] Move microprofile impl to Apache TomEE

[Raymond Augé]

+1

On Mon., Jun. 6, 2022, 06:43 Romain Manni-Bucau, 
wrote:

> Hi,
>
> Think it makes sense since most of contributors of the original projects
> abandonned Microprofile due to the policy they apply to the project AFAIK
> and there is not much interest there anymore AFAIK.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github
>  | LinkedIn
>  | Book
> 
>
>
> Le lun. 6 juin 2022 à 11:00, fpapon  a écrit :
>
>> Hi all,
>>
>> I would like to start a thread to discuss about the future of the Apache
>> Geronimo Microprofile implementation:
>>
>> https://geronimo.apache.org/microprofile/
>>
>> As we can see, we don't have a lot of traction about the maintenance of
>> the implementation to be up-to-date with the Microprofile specification.
>>
>> The J2EE Geronimo server is no longer exist and at Apache, the active EE
>> server seems to be Apache TomEE.
>>
>> May be it could make more sense to move the Microprofile implementation
>> to the Apache TomEE umbrella.
>>
>> WDYT?
>>
>> regards,
>>
>> --
>> --
>> François
>>
>>

Re: [VOTE] Release Activation 2.0.0-M1

[Raymond Augé]

+1 (binding)

On Sun., May 15, 2022, 5:58 a.m. Jean-Louis MONTEIRO, 
wrote:

> +1
>
> Same feedback, I'd go for a final. There is no work remaining as far as I
> can tell
>
> Le dim. 15 mai 2022 à 09:03, Romain Manni-Bucau  a
> écrit :
>
>> Hi
>>
>> If we are confident to match javax/jakarta namespace change why not doing
>> a final? Errors/missing features could go in bugs.
>> Issue with milestones is the tooling support and proposed updates vs
>> version policies so if we can avoid it I would be for it but not sure if I
>> missed sthg.
>>
>> Le dim. 15 mai 2022 à 07:29, Jean-Baptiste Onofré  a
>> écrit :
>>
>>> +1 (binding)
>>>
>>> Regards
>>> JB
>>>
>>> On Sat, May 14, 2022 at 11:00 PM David Blevins 
>>> wrote:
>>> >
>>> > Hey All,
>>> >
>>> > We're thinking to do a release on the TomEE side and this is one of
>>> the snapshot dependencies we have.  I've prepped a 2.0.0-M1 with the idea
>>> that being a milestone it should be fairly non-controversial to propose
>>> without a heads up and I haven't checked the TCK status.  I know we're not
>>> yet actively running the signature tests on the TomEE side.
>>> >
>>> > I propose we release 2.0.0-M1 so we have some non-snapshots to work
>>> with and come back to 2.0.0 as things look 100% on all fronts
>>> >
>>> > Staging Maven repository:
>>> >
>>> >  -
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1153/
>>> >
>>> > The only change is conversion from javax to the jakarta namespace via
>>> contributor Richard Zowalla.
>>> >
>>> >
>>> > Please vote to approve this release:
>>> > [ ] +1 Approve the release
>>> > [ ]  0 Abstain (please provide specific comments)
>>> > [ ] -1 Don't approve the release (please provide specific comments)
>>> >
>>> > This vote will be open for at least 72 hours.
>>> >
>>> > -David
>>> >
>>>
>>
>
> --
> Jean-Louis
>

Re: [VOTE] Release Mail 2.0.0-M1

[Raymond Augé]

+1 (binding)

On Sun., May 15, 2022, 5:57 a.m. Jean-Louis MONTEIRO, 
wrote:

> +1
>
> But I agree with Romain, don't think there is remaining work on this one
> for now. So wondering why we need a milestone.
> We ran the unit tests and we ran all the platform TCK for Mail and
> everything is passing.
>
> Le dim. 15 mai 2022 à 11:31, Zowalla, Richard <
> richard.zowa...@hs-heilbronn.de> a écrit :
>
>> Side note: JL did run the mail tck:
>> https://tck.work/tomee/tests?build=1651841331620=com.sun.ts.tests.javamail
>>
>> Gruß
>> Richard
>> --
>> *Von:* David Blevins 
>> *Gesendet:* Samstag, 14. Mai 2022 23:27:29
>> *An:* dev@geronimo.apache.org
>> *Betreff:* [VOTE] Release Mail 2.0.0-M1
>>
>> Hey All,
>>
>> If I was thinking ahead I'd have put these both in the same staging repo
>> and vote :)
>>
>> Staging Maven repository:
>>
>> -
>> https://repository.apache.org/content/repositories/orgapachegeronimo-1153/
>>
>> The only change is conversion from javax to the jakarta namespace via
>> contributor Richard Zowalla and a change from "javamail" to simply "mail"
>>
>>
>> Please vote to approve this release:
>> [ ] +1 Approve the release
>> [ ]  0 Abstain (please provide specific comments)
>> [ ] -1 Don't approve the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> -David
>>
>>
>
> --
> Jean-Louis
>

Re: [VOTE] Apache XBean 4.21 release

[Raymond Augé]

+1

On Wed, Apr 13, 2022 at 10:26 AM Romain Manni-Bucau 
wrote:

> +1
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | 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 mer. 13 avr. 2022 à 15:53, Jean-Baptiste Onofré  a
> écrit :
>
>> Hi everyone,
>>
>> I submit Apache XBean 4.21 release to your vote.
>>
>> This release includes:
>> - Spring 4 & 5 support, up to Spring 5.3.19
>> - ASM 9.3 update
>>
>> Release Notes:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310312=12351586
>>
>> Staging Maven repository:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-1152/
>>
>> Staging dist repository:
>> https://dist.apache.org/repos/dist/dev/geronimo/xbean/
>>
>> Please vote to approve this release:
>> [ ] +1 Approve the release
>> [ ] -1 Don't approve the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Regards
>> JB
>>
>

-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Re: Batchee coming release 1.0.1

[Raymond Augé]

+1

Ray

On Tue, Oct 26, 2021 at 5:33 AM Jean-Baptiste Onofre 
wrote:

> +1
>
> Regards
> JB
>
> > Le 26 oct. 2021 à 10:07, Romain Manni-Bucau  a
> écrit :
> >
> > Hi all,
> >
> > I pushed a few changes on BatchEE, highlights are:
> >
> > 1. drop of cxf 2 client support (think it is way overdue)
> > 2. adding basic spring-boot batchee UI integration
> >
> > I'd like to release it, any objection?
> >
> > Romain Manni-Bucau
> > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
>
>

-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Re: [VOTE] geronimo-javamail_1.6_(provider|mail) 1.0.1 (reroll)

[Raymond Augé]

+1

Ray

On Fri, Oct 15, 2021 at 9:55 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> +1 (thx, JL)
>
> Am Freitag, dem 15.10.2021 um 15:47 +0200 schrieb Jean-Louis MONTEIRO:
> > Hi!
> >
> > I’d like to call a VOTE on the geronimo-javamail_1.6_(provider|mail)
> > 1.0.1
> > Importante note: we previously voted for the spec part. This vote is
> > for the provider and the mail core.
> >
> > This is a re-roll because we were missing the spec update.
> >
> > Here is the staging repo
> >
> https://repository.apache.org/content/repositories/orgapachegeronimo-1143
> >
> > And the source jar which is voted on
> >
> https://dist.apache.org/repos/dist/dev/geronimo/javamail/geronimo-javamail_1.6-1.0.1-source-release.zip
> >
> > Git tag
> >
> https://github.com/apache/geronimo-javamail/tree/geronimo-javamail_1.6-1.0.1
> >
> > My key can be found at
> > https://svn.apache.org/repos/asf/geronimo/KEYS
> >
> > please VOTE
> > [+1] all fine, ship it
> > [+0] don't care
> > [-1] stop, because ${reason}
> >
> > The VOTE is open for 72h.
> >
> >
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow, Java Champion

Re: [VOTE] geronimo-javamail_1.6_spec 1.0.1

[Raymond Augé]

+1

Ray

On Fri., Oct. 8, 2021, 11:17 a.m. Cesar Hernandez, 
wrote:

> +1, thank you!
>
> El vie, 8 oct 2021 a las 7:32, Jean-Louis MONTEIRO ()
> escribió:
>
>> +1
>>
>> And yes I'll do provider and mail at the same time after. Wanted to get
>> the spec first and separately.
>>
>> Le ven. 8 oct. 2021 à 15:08, Zowalla, Richard <
>> richard.zowa...@hs-heilbronn.de> a écrit :
>>
>>> +1 (downstream mail & provider would be great in terms of TLS 1.2+
>>> compatibility)
>>>
>>> Am Freitag, dem 08.10.2021 um 15:05 +0200 schrieb Romain Manni-Bucau:
>>> > +1 (I assume a follow up vote can be needed for
>>> >
>>> https://svn.apache.org/repos/asf/geronimo/javamail/trunk/geronimo-javamail_1.6/
>>> > to get it fully out the door? if you want you can run both at the
>>> > same time making downstream one dependent on this one ;))
>>> >
>>> > Romain Manni-Bucau
>>> > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
>>> >
>>> >
>>> > Le ven. 8 oct. 2021 à 10:13, Jean-Baptiste Onofré  a
>>> > écrit :
>>> > > +1 (binding)
>>> > >
>>> > > Regards
>>> > > JB
>>> > >
>>> > > On 07/10/2021 21:30, Jean-Louis MONTEIRO wrote:
>>> > > > Hi!
>>> > > >
>>> > > > I’d like to call a VOTE on the geronimo-javamail_1.6_spec 1.0.1
>>> > > >
>>> > > > Here is the staging repo
>>> > > >
>>> > >
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1141
>>> > > <
>>> > >
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1141
>>> > > >
>>> > > >
>>> > > > And the source jar which is voted on
>>> > > >
>>> > >
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1141/org/apache/geronimo/specs/geronimo-javamail_1.6_spec/1.0.1/geronimo-javamail_1.6_spec-1.0.1-source-release.zip
>>> > >
>>> > > > <
>>> > >
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1141/org/apache/geronimo/specs/geronimo-javamail_1.6_spec/1.0.1/geronimo-javamail_1.6_spec-1.0.1-source-release.zip
>>> > > >
>>> > > >
>>> > > > SVN tag
>>> > > >
>>> > >
>>> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.6_spec-1.0.1/
>>> > >
>>> > > > <
>>> > >
>>> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.6_spec-1.0.1/
>>> > > >
>>> > > >
>>> > > > My key can be found at
>>> > > > https://svn.apache.org/repos/asf/geronimo/KEYS
>>> > > > 
>>> > > >
>>> > > > please VOTE
>>> > > > [+1] all fine, ship it
>>> > > > [+0] don't care
>>> > > > [-1] stop, because ${reason}
>>> > > >
>>> > > > The VOTE is open for 72h.
>>> > > >
>>> > > > --
>>> > > > Jean-Louis
>>> --
>>> Richard Zowalla, M.Sc.
>>> Research Associate, PhD Student | Medical Informatics
>>>
>>> Hochschule Heilbronn – University of Applied Sciences
>>> Max-Planck-Str. 39
>>> D-74081 Heilbronn
>>> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
>>> mail: richard.zowa...@hs-heilbronn.de
>>> web: https://www.mi.hs-heilbronn.de/
>>>
>>
>>
>> --
>> Jean-Louis
>>
>
>
> --
> Atentamente:
> César Hernández.
>

Re: [VOTE] - Move Svn to Gitbox

[Raymond Augé]

+1

Ray

On Sat., May 15, 2021, 2:25 a.m. ,  wrote:

> Hi,
>
> I would like to start a vote about moving some projects from svn to gitbox:
>
> - http://svn.apache.org/repos/asf/geronimo/xbean/
>
> - http://svn.apache.org/repos/asf/geronimo/javamail/
>
> - http://svn.apache.org/repos/asf/geronimo/components/txmanager/
>
>
> Discussion thread:
>
> -
> https://lists.apache.org/thread.html/r5a89c97f4afb2cf900277c14fd27cb14c463855ca0d4093b9921e80a%40%3Cdev.geronimo.apache.org%3E
>
>
> Please vote:
>
>
> [ ] +1 Approve
> [ ] -1 Don't approve (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> regards,
>
> --
> Françoisfpa...@apache.org
>
>

Re: [DISCUSS] - SVN to Gitbox

[Raymond Augé]

+1

Ray

On Tue, May 11, 2021 at 9:15 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> > 1. enable PR on github (today it is a mess for external users)
>
> I can only give +1 to this point ;)
>
>
> Am Dienstag, den 11.05.2021, 15:13 +0200 schrieb Romain Manni-Bucau:
> > Guess we should stick to what we are used to.
> > The most visible part is likely the release so I'm tempted to say we
> > do one repo per atomic release.
> > For specs it likely means one repo per spec (but we can automate it
> > or work with infra to bulk migrate it).
> > Will maybe hurt a bit right now but will:
> >
> > 1. enable PR on github (today it is a mess for external users)
> > 2. make releases easier (monorepo failed, happy we never moved to
> > that ;))
> >
> > Romain Manni-Bucau
> > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
> >
> >
> > Le mar. 11 mai 2021 à 14:00, Jean-Baptiste Onofre  a
> > écrit :
> > > Hi Mark,
> > >
> > > I guess you mean for the release ?
> > >
> > > If we agree to have bunch of tag, we can have spec in a single repo
> > > (it’s what I’m doing at ServiceMix).
> > >
> > > But I guess it would be cleaner to have a dedicated repo per spec
> > > (less convenient anyway).
> > >
> > > Regards
> > > JB
> > >
> > > > Le 11 mai 2021 à 13:56, Mark Struberg  a écrit
> > > :
> > > >
> > > > specs could be tricky. We'd need to do every single spec as own
> > > git repo, isn't?
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > >> Am 11.05.2021 um 05:39 schrieb fpa...@apache.org:
> > > >>
> > > >> Hi,
> > > >>
> > > >> I would like to start a discussion about moving some of our
> > > project
> > > >> repositories from svn to gitbox.
> > > >>
> > > >>
> > > >> I think we can start with this projects:
> > > >>
> > > >> - http://svn.apache.org/repos/asf/geronimo/xbean/
> > > >>
> > > >> - http://svn.apache.org/repos/asf/geronimo/javamail/
> > > >>
> > > >> - http://svn.apache.org/repos/asf/geronimo/components/txmanager/
> > > >>
> > > >> - http://svn.apache.org/repos/asf/geronimo/specs/
> > > >>
> > > >>
> > > >> Here are the current Geronimo gitbox projects:
> > > >>
> > > >> https://gitbox.apache.org/repos/asf#geronimo
> > > >>
> > > >>
> > > >> Any objection? Don't hesitate to add other project you want to
> > > move.
> > > >>
> > > >> regards,
> > > >>
> > > >> --
> > > >> François
> > > >> fpa...@apache.org
> > > >>
> > > >
> > >
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: [VOTE] Release Apache BatchEE 1.0.0

[Raymond Augé]

+1

Ray

On Sat, May 8, 2021 at 12:31 PM Romain Manni-Bucau 
wrote:

> +1
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | 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 sam. 8 mai 2021 à 10:31, Jean-Baptiste Onofre  a
> écrit :
>
>> +1 (binding)
>>
>> Regards
>> JB
>>
>> Le 8 mai 2021 à 09:51, Mark Struberg  a écrit :
>>
>> hi lords and ladies!
>>
>> I want to call a VOTE on releasing Apache BatchEE 1.0.0
>> This is mainly an update to JavaEE8 and a few bug fixes.
>>
>> We fixed the following tickets.
>>
>> Bug
>>
>>- [BATCHEE-126 <https://issues.apache.org/jira/browse/BATCHEE-126>] -
>>upgrade to tomee-8.0.6
>>- [BATCHEE-149 <https://issues.apache.org/jira/browse/BATCHEE-149>] -
>>BatchCDIInjectionExtension should only use CDI.current() if container is
>>really started
>>- [BATCHEE-150 <https://issues.apache.org/jira/browse/BATCHEE-150>] -
>>JDBCDictionary deleteStepExecution did contain invalid SQL
>>- [BATCHEE-151 <https://issues.apache.org/jira/browse/BATCHEE-151>] -
>>starting batchee-cli in parallel might cause race conditions when 
>> unpacking
>>WARs
>>
>> New Feature
>>
>>- [BATCHEE-148 <https://issues.apache.org/jira/browse/BATCHEE-148>] -
>>Upgrade BatchEE-1.0.0 to EE8
>>
>> Task
>>
>>- [BATCHEE-147 <https://issues.apache.org/jira/browse/BATCHEE-147>] -
>>upgrade to latest apache parent
>>
>>
>>
>> The staging repository is hosted here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1007/
>>
>> The source zip can be found here:
>>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1007/org/apache/batchee/batchee/1.0.0/
>> sha1 is da2990a42caaa639a50df03de3eaec4f6548a8bc
>>
>> Please VOTE
>>
>> [+1] ship it!
>> [+0] don't care
>> [-1] stop, there's a ${showstopper}
>>
>> The VOTE is open for 72h
>>
>> LieGrue,
>> strub
>>
>>
>>

-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: [VOTE] Apache Bean 4.19 release

[Raymond Augé]

+1

Ray

On Tue., Apr. 13, 2021, 3:47 a.m. Romain Manni-Bucau, 
wrote:

> +1, thks a lot JB
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github
>  | LinkedIn
>  | Book
> 
>
>
> Le mar. 13 avr. 2021 à 08:55, Jean-Louis MONTEIRO  a
> écrit :
>
>> +1
>>
>> Le mar. 13 avr. 2021 à 07:00, Jean-Baptiste Onofre  a
>> écrit :
>>
>>> Hi everyone,
>>>
>>> I submit XBean 4.19 to your vote.
>>>
>>> This release especially includes:
>>> - Upgrade to ASM 9.1
>>> - Fix a NPE when the superclass is not set in the bundle finder
>>> - Fix OSGi headers in asm9 shaded artifact
>>>
>>> Release Notes:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310312=12348824
>>>
>>> Maven Staging Repository:
>>>
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1138/
>>>
>>> Dist Staging Repository:
>>> https://dist.apache.org/repos/dist/dev/geronimo/xbean/4.19/
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Don't approve the release (please provide specific comments)
>>>
>>> This vote will be open for at least 72 hours.
>>>
>>> Thanks !
>>> Regards
>>> JB
>>>
>>
>>
>> --
>> Jean-Louis
>>
>

Re: [arthur] Launching openjpa/derby support?

[Raymond Augé]

urce)
>> at
>> org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(Unknown
>> Source)
>> at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(Unknown Source)
>> at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(Unknown
>> Source)
>> at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
>> at org.apache.derby.impl.sql.GenericStatement.prepareStorable(Unknown
>> Source)
>> at
>> org.apache.derby.iapi.sql.dictionary.SPSDescriptor.compileStatement(Unknown
>> Source)
>> at
>> org.apache.derby.iapi.sql.dictionary.SPSDescriptor.prepareAndRelease(Unknown
>> Source)
>> at
>> org.apache.derby.iapi.sql.dictionary.SPSDescriptor.getPreparedStatement(Unknown
>> Source)
>> at
>> org.apache.derby.iapi.sql.dictionary.SPSDescriptor.getPreparedStatement(Unknown
>> Source)
>> at org.apache.derby.impl.sql.compile.ExecSPSNode.generate(Unknown Source)
>> at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
>> at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
>> at
>> org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
>> Source)
>> ... 34 more
>>
>> Overall it is mainly about making derby graalifyable I think.
>> I need to switch to another topic for a moment so if anyone wants to
>> continue the experimentations just jump in.
>>
>> The small side notes I can gives are:
>>
>> 1. we can do a dbcp2-knight and a commons-logging-knight (for now they
>> are in openjpa one - it is commented as such), these ones should be easy
>> since already coded, just not packaged properly
>> 2. the immediate fix for deby will likely sit either
>> in org.apache.geronimo.arthur.knight.derby.DerbyExtension or a substitution
>> in the same module
>> 3. if easier we can use another database (h2 does not work and will
>> likely not work in embedded mode so hsqldb can be saner - at least I don't
>> know for this one)
>>
>> If you are motivated to proove openjpa runs in native mode and finish
>> this branch, don't hesitate to answer this thread, I'd also be happy to
>> discuss more on slack or by mail details if it helps.
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> <https://rmannibucau.metawerx.net/> | 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>
>>
>

-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow