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

2022-07-11 Thread 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  |  Blog
>  | Old Blog
>  | Github
>  | LinkedIn
>  | Book
> 
>
>
> 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: Moving Mail, Activation, Transaction and Connector to Apache TomEE (was Re: [DISCUSS] Move microprofile impl to Apache TomEE)

2022-07-07 Thread Romain Manni-Bucau 
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  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



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
> > > > >
> > > >
> >
> >
>

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

2022-07-07 Thread Zowalla, Richard 
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
> > > > 
> > > 
> 
> 


smime.p7s
Description: S/MIME cryptographic signature

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

2022-06-20 Thread Jean-Louis MONTEIRO 
+1

Le dim. 19 juin 2022 à 16:02, Jean-Baptiste Onofré  a
écrit :

> Hi,
>
> Activation, transaction and connector are used also in Aries, ActiveMQ,
> Karaf.
>
> So, no problem for me as soon as we keep the "generic" aspect (not
> TomEE too centric).
>
> Regards
> JB
>
> On Tue, Jun 14, 2022 at 6:29 PM David Blevins 
> wrote:
> >
> > 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
> > >
> >
>


-- 
Jean-Louis

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

2022-06-19 Thread Jean-Baptiste Onofré 
Hi,

Activation, transaction and connector are used also in Aries, ActiveMQ, Karaf.

So, no problem for me as soon as we keep the "generic" aspect (not
TomEE too centric).

Regards
JB

On Tue, Jun 14, 2022 at 6:29 PM David Blevins  wrote:
>
> 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
> >
>

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

2022-06-17 Thread David Jencks 



> On Jun 17, 2022, at 11:23 AM, David Blevins  wrote:
> 
> 
>> On Jun 14, 2022, at 10:09 PM, David Jencks  wrote:
>> 
>> I think each impl. needs to be in its own git repo, I’m not sure which 
>> already are.
> 
> Agree.  Currently connector and txmanager are in the same git repo.
> 
>> 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.
> 
> I don't know if it helps the conversation, but we need a different version 
> that's incompatible to what Aries and ActiveMQ uses.We would be 
> developing and implementing jakarta.* implementations they couldn't use.  For 
> them to switch from javax to jakarta, they'd need to change all their 
> dependencies anyway.

I expect eventually they will make the switch.

> 
> Really the question being asked is does anyone mind if we develop separate 
> Jakarta versions of the APIs on the TomEE side?  It would be a little easier 
> for us.
> 

Do you expect to have a new unrelated tx manager implementation?  I rather 
expected something mostly changed via sed, and a major version bump.  I don’t 
think you put the jakarta TomEE in a new repo, did you?

However, I don’t really care as long as you leave a really obvious note behind 
about where development has moved to.

David Jencks
> 
> -David
> 
>>> On Jun 14, 2022, at 9:36 AM, Romain Manni-Bucau  
>>> 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  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
 
>>> 
>> 
>

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

2022-06-17 Thread Romain Manni-Bucau 
Le ven. 17 juin 2022 à 20:23, David Blevins  a
écrit :

>
> > On Jun 14, 2022, at 10:09 PM, David Jencks 
> wrote:
> >
> > I think each impl. needs to be in its own git repo, I’m not sure which
> already are.
>
> Agree.  Currently connector and txmanager are in the same git repo.
>
> > 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.
>
> I don't know if it helps the conversation, but we need a different version
> that's incompatible to what Aries and ActiveMQ uses.We would be
> developing and implementing jakarta.* implementations they couldn't use.
> For them to switch from javax to jakarta, they'd need to change all their
> dependencies anyway.
>
> Really the question being asked is does anyone mind if we develop separate
> Jakarta versions of the APIs on the TomEE side?  It would be a little
> easier for us.
>


Strictly speaking you dont even need to ask so maybe ask once done and if
there would be any merge need if it eases work for you ;).


>
> -David
>
> >> On Jun 14, 2022, at 9:36 AM, Romain Manni-Bucau 
> 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 
> 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
> >> >
> >>
> >
>
>

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

2022-06-17 Thread David Blevins 

> On Jun 14, 2022, at 10:09 PM, David Jencks  wrote:
> 
> I think each impl. needs to be in its own git repo, I’m not sure which 
> already are.

Agree.  Currently connector and txmanager are in the same git repo.

> 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.

I don't know if it helps the conversation, but we need a different version 
that's incompatible to what Aries and ActiveMQ uses.We would be developing 
and implementing jakarta.* implementations they couldn't use.  For them to 
switch from javax to jakarta, they'd need to change all their dependencies 
anyway.

Really the question being asked is does anyone mind if we develop separate 
Jakarta versions of the APIs on the TomEE side?  It would be a little easier 
for us.


-David

>> On Jun 14, 2022, at 9:36 AM, Romain Manni-Bucau  
>> 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  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
>> > 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

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

2022-06-15 Thread Zowalla, Richard 
Am Dienstag, dem 14.06.2022 um 22:09 -0700 schrieb David Jencks:
> 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.

From a quick look at Apache Aries, I think, that you are right. In
addition, Apache ActiveMQ is using the tx manager in some modules too.


Gruß
Richard


smime.p7s
Description: S/MIME cryptographic signature

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

2022-06-15 Thread fpapon 

No objection from my side.

regards,

François

On 14/06/2022 18:29, David Blevins wrote:

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


--
--
François

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

2022-06-14 Thread 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  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  > 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
> > 
>

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

2022-06-14 Thread Romain Manni-Bucau 
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  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
> >
>
>

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

2022-06-14 Thread David Blevins 
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
> 



smime.p7s
Description: S/MIME cryptographic signature