Re: [jca-dev] Jakarta EE 10 for Connectors

["Nathan Rauh" <nathan.rauh@xxxxxxxxxx>]

I'm not aware of
any features to add for Jakarta Connectors/JCA either and I'd vote against
the additional rename under issue #69 because it causes more churn after
having already done a massive package rename in Jakarta EE 9 --  it
would actually cause more problems than it would solve, making a transition
to the jakarta namespace less straightforward and putting additional burden
on those who already had made the transition.  Meanwhile, anyone who
is impacted (because they import cci.*) by the addition of java.lang.Record
will already have to make a change regardless so it should not be a big
deal to add in the explicit import of the fully qualified class vs updating
to a new class name.  The former can usually be done in one spot in
the file vs the latter which might be all over the place.




From:
       "Steve
Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To:
       jca
developer discussions <jca-dev@xxxxxxxxxxx>
Date:
       03/17/2021
11:10 AM
Subject:
       [EXTERNAL]
[jca-dev] Jakarta EE 10 for Connectors
Sent
by:        "jca-dev"
<jca-dev-bounces@xxxxxxxxxxx>

---

Hi,

 

If we want to make an update for Jakarta EE 10 the team need to put together a release plan by April 15^th. Currently we don’t really have any substantive feature issues in the GitHub repo.

 

We do have the clash with java.lang.Record to consider see Consider renaming resource.cci.Record to avoid collisions with java.lang.Record · Issue #69 · eclipse-ee4j/jca-api (github.com)

 

If anybody want to do any new features or changes for Jakarta EE 10 can you add an issue to the GitHub repo. I can then tag the issue for a 2.x or 3.0 milestone and create the release plan by the deadline.

 

Thanks

 

Steve

 

 _______________________________________________
jca-dev mailing list
jca-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jca-dev