Re: [jakarta.ee-community] Thoughts on JakartaEE

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

On 9/24/19 3:21 PM, Werner Keil wrote:
> You discovered that EclipseLink has more than Bugzilla and the more 
> recent important ones should be there. Bugzilla has many, but Hibernate 
> ORM alone got 2861 open issues in its JIRA, so does that mean you 
> consider both abandonware? ;-)

Just for the record: some projects are closing defined set of existing 
issues (ie 3-5years old) at some defined points (ie after each major 
release) to keep the numbers nice, bugs as such under control and 
end-users happy. It has some benefits but this has never been the case 
with EclipseLink project - at least I'm not aware of an issue which 
would be closed just because of its age. This should explain why there 
is so many existing issues where some of them are from 2007 (the year 
when TopLink code was donated to Eclipse Foundation and EclipseLink 
project was started. Original TopLink code dates back to 1996, if we 
consider Java version only).

thanks,
--lukas

> The "incremental vs. Big bang" discussion was about refactoring from 
> javax to jakarta namespaces and not how many new specs Jakarta EE 9, 10 
> or 11 might include. For 8 everything was put in a new Maven Groupid but 
> that is not the biggest effort.
> Think of JPA alone there are many XML files referring to Java or JCP.
> Whether all get changed with Jakarta EE 9 or only the most commonly used 
> remains to be seen.
>
> Werner
>
> carlos andres de la rosa <kusanagi12002@xxxxxxxxx 
> <mailto:kusanagi12002@xxxxxxxxx>> schrieb am Di., 24. Sep. 2019, 13:46:
>
>     +1 taking into account what cen says for me now have more much sense
>     the incremental approach than try to migrate everything at once.
>
>     IMHO
>
>
>     On Tue, Sep 24, 2019 at 1:33 PM Emmanuel Bernard
>     <ebernard@xxxxxxxxxx <mailto:ebernard@xxxxxxxxxx>> wrote:
>
>         +1. I like what you wrote Cen. It does matches my perspective as
>         well.
>
>
>         On 23 Sep 2019, at 18:47, cen wrote:
>
>          > Hi,
>          >
>          > After reading a ton of mailing list material and blog posts
>         I'd like
>          > to share some thoughts on JakartaEE.
>          >
>          > I use a lot of JavaEE and MP daily and contribute to one of MP
>          > framework implementations.
>          >
>          >
>          > The javax naming is very unfortunate but won't really be a
>         big problem
>          > for us microservice users since we can update one service at
>         a time.
>          > Other than refactoring costs I don't see anything
>         problematic, I think
>          > application server users will have much more trouble.
>          >
>          > MP was the best thing that happened to JavaEE because it
>         allowed us to
>          > take the stable and mature modules from JavaEE and combine
>         them with
>          > modern approaches that were missing in the spec. Seeing how
>         successful
>          > MP has been so far, I wouldn't merge the projects but
>         collaboration
>          > between projects to make specs more interop is welcome.
>         Duplicating
>          > specs for roughly the same things would be the major fail.
>          >
>          > I have mixed feelings about JakartaEE adding a ton of new
>         features to
>          > attract new users. While some new features would be welcome,
>         I see the
>          > core modules pretty feature complete. I am not sure people would
>          > switch massively to JakartaEE for any reason but I do know
>         existing
>          > developers will probably stay if platform feels alive which
>         was not
>          > the case for the past few years. As an existing user I am more
>          > concerned about the state of some important reference
>         implementations
>          > with long standing bugs which are an annoyance in day-to-day
>         work.
>          > Looking at bugs.eclipse.org <http://bugs.eclipse.org> -
>         Eclipselink for example screams of
>          > abandonware although now that all projects are on github
>         contributing
>          > is thankfully much easier. I already had some positive
>         experience
>          > contributing to upstream RI so that's feels good.
>          >
>          >
>          > Best regards, cen
>          >
>          >
>          >
>          > _______________________________________________
>          > jakarta.ee-community mailing list
>          > jakarta.ee-community@xxxxxxxxxxx
>         <mailto:jakarta.ee-community@xxxxxxxxxxx>
>          > To change your delivery options, retrieve your password, or
>          > unsubscribe from this list, visit
>          > https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
>
>         _______________________________________________
>         jakarta.ee-community mailing list
>         jakarta.ee-community@xxxxxxxxxxx
>         <mailto:jakarta.ee-community@xxxxxxxxxxx>
>         To change your delivery options, retrieve your password, or
>         unsubscribe from this list, visit
>         https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
>
>
>
>     -- 
>
>     *Carlos Andres De La Rosa | Software Architect*
>
>     Mobile: + <tel:%2B57-3163226522>32465445631
>
>     Skype: carlosa.dlr
>
>     _______________________________________________
>     jakarta.ee-community mailing list
>     jakarta.ee-community@xxxxxxxxxxx
>     <mailto:jakarta.ee-community@xxxxxxxxxxx>
>     To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
>
>
> _______________________________________________
> jakarta.ee-community mailing list
> jakarta.ee-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakarta.ee-community