Re: [eclipselink-dev] [External] : EclipseLink 3.0.1 release

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

Hi Arjan,

On 3/15/21, 9:40 PM, "eclipselink-dev on behalf of arjan tijms" <eclipselink-dev-bounces@xxxxxxxxxxx on behalf of arjan.tijms@xxxxxxxxx> wrote:

    Hi,
    Would be good if EclipseLink 3.0.1 (or whatever the exact next version is), could be part of GlassFish 6.1.0. As GlassFish 6.1.0 partially has the same blockers, it sees the timelines would match to make this feasible.

That is our main goal __ (I need updated EclipseLink/MOXy for Metro as well, Jersey may want to pick it up too) The biggest issue right now (as I see it) is the speed of the spec committee :-/ While they've made the release process of spec artifacts simpler (which itself took about a month) I haven't seen any improvement on their execution speed yet, so I'm not sure the simplified process is big win over the 2weeks long ballot in terms of review/waiting time... it seems it only requires less paper-work so far :-/ 

btw, Arjan, will you be able to release ha-api so I can include it in upcoming Metro?

thanks,
--lukas

    Kind regards,
    Arjan





    On Mon, Mar 15, 2021 at 8:54 PM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> wrote:


    Hi,

    On 3/15/21, 8:29 PM, "eclipselink-dev on behalf of William Dazey" <eclipselink-dev-bounces@xxxxxxxxxxx on behalf of dazeydev.3@xxxxxxxxx> wrote:

        Hello!
        Are there any plans to release EclipseLink 3.0.1 soon?

    Another "blocker" for RC build is that we want to update few API dependencies to upcoming versions and even though most of them are already available in staging repo, we don't want to leak them out before their releases are approved by spec committee. Two of them are already on review for some time[1][2], for MOXy, we also need XML Binding API where I'm waiting for TCK test run on JDK 11 (which itself takes ~8 hours, I expect having this ready for review this week). Other 2 API dependencies updates I'm aware of are not that important from EclipseLink point of view.

    thanks,
    --lukas

    [1]: https://github.com/jakartaee/specifications/pull/336 <https://urldefense.com/v3/__https://github.com/jakartaee/specifications/pull/336__;!!GqivPVa7Brio!JaqM2wHbcLniOcV2365vWsfvdT8uNWjdoLmvi1lPKIx2ToRJqhhhVIjS5HcSuMqQXwg$>
    [2]: https://github.com/jakartaee/specifications/pull/339 <https://urldefense.com/v3/__https://github.com/jakartaee/specifications/pull/339__;!!GqivPVa7Brio!JaqM2wHbcLniOcV2365vWsfvdT8uNWjdoLmvi1lPKIx2ToRJqhhhVIjS5HcSbw3ZJGg$>


     One specific
        reason to release soon would be to fix the performance regression in
        3.0.0, which is fixed in
        https://urldefense.com/v3/__https://github.com/eclipse-ee4j/eclipselink/pull/1010__;!!GqivPVa7Brio!Ndo_LLldmvDYEKHGVdLqekkTNXG3KnHwivGJKbSyGCTqxGVOI8sulFr8bzXftYPpXsU$ . There is a work
        around, yes, but it would be nice to not have to do that.

        Thanks,
        Will Dazey
        _______________________________________________
        eclipselink-dev mailing list
        eclipselink-dev@xxxxxxxxxxx
        To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/eclipselink-dev__;!!GqivPVa7Brio!Ndo_LLldmvDYEKHGVdLqekkTNXG3KnHwivGJKbSyGCTqxGVOI8sulFr8bzXfUQAe6Nw$ 

    _______________________________________________
    eclipselink-dev mailing list
    eclipselink-dev@xxxxxxxxxxx
    To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipselink-dev <https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/eclipselink-dev__;!!GqivPVa7Brio!JaqM2wHbcLniOcV2365vWsfvdT8uNWjdoLmvi1lPKIx2ToRJqhhhVIjS5HcSRNgPRqw$>