I go back and forth on whether to shut G down completely. Perhaps it would be
useful to inventory which parts are used by which other projects? Off the top
of my head….
Specs …. who uses G’s and who has their own?
Components…. I think there are several users of the transaction manager, I
A valid point is activity related to G happens elsewhere, However elsewhere
is not "tomee" which would make things simple to move but A, B, C so
shutting down G is likely the easiest solution for G itself but also the
worse for all its dependent projects - and ASF consistency since G is now
seen
I’ve monitored G for several years since my departure. For me, JEE is not my
main area of focus and as such, I’ve invested little time in the project apart
from reading the e-mail threads. This is a community decision and posting the
discussion to dev@ is the right venue.
As an inactive
On March 8, 2017 at 10:44:45 AM, Mark Struberg (strub...@yahoo.de) wrote:
Alan, I understand that you don't want to put much more energy into this
project. That is totally understandable and fine.
But while you are PMC chair you still cannot declare that the project is dead
as long as there are
unsubscribe
On Wed, Mar 8, 2017 at 6:44 PM, Mark Struberg wrote:
> Alan, I understand that you don't want to put much more energy into this
> project. That is totally understandable and fine.
> But while you are PMC chair you still cannot declare that the project is
> dead as
Alan, I understand that you don't want to put much more energy into this
project. That is totally understandable and fine.
But while you are PMC chair you still cannot declare that the project is dead
as long as there are enough PMC members still active to keep the project going.
Before we
I agree and I even acknowledged that below, but what I feel Mark and you are
not acknowledging is that the interest/activity is for a smaller subset of JEE.
Of that subset, even you list the OSS projects that are supporting the JEE
bits that are still relevant. They have active communities
Thanks Alan! Many thanks for all you've done!
I think we all agree that it is time to retire the Geronimo Server portions
of the project.
My apologies to Romain, Mark, David, and others, but:
I think the entire project should be retired. I confess that I am not
closely following the dev list (I
I share that vision (the one of Mark).
The ee-commons part is really used and still active (even if in maintenance
mode for several parts) and we need to ensure other projects can still rely
on it (karaf, tomee, owb, meecrowave, openjpa, ... plus several open source
ones).
EE is also not dead,
I see no lack of interest in Java EE to be honest. Of course Microservices are
currently spilled high on the hype cycle, but that will quickly blow up imo.
MS architecture is only very good for a certain kind of application. For most
business apps the granularity is way too fine grain and the
10 matches
Mail list logo