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 <fpa...@apache.org> 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
