A FAQ is a great
idea. Easy way to amend the Release Plan without requiring a rev
and review. I will start one and have it ready for a review at tomorrow's
(My apologies, but Lotus Notes is
just terrible at internet-style replies to emails... I've embedded
my comments below.)
wrote on 03/08/2020 08:13:53:
> From: arjan tijms <arjan.tijms@xxxxxxxxx> > To: jakartaee-platform developer
discussions <jakartaee-platform- > dev@xxxxxxxxxxx> > Date: 03/08/2020 08:14 > Subject: [EXTERNAL] Re: [jakartaee-platform-dev]
Understanding a few > javax->jakarta decisions > Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx > > > > On Saturday, March 7, 2020, Bill Shannon <bill.shannon@xxxxxxxxxx>
wrote: > Kevin will tell me if I got
this wrong, but... Here's what I remember...
> Scott Kurz wrote on 3/6/20 1:40
PM: > Late to the discussion, I wanted
to see where we'd settled on the EE > 9 plan questions (I see some discussion on the various lists) > > 1. Whether it is OK to add generic support in EE 9 along with the
package move > It's ok, but you'll need to
file your own release plan since you're > stepping outside what the platform release plan says. > > The way I remember / interpreted it is that returning say Class<?>
> instead of Class is okay, but accepting say Map<String, ?> instead
> of Map is not okay. > > Not saying that is what was decided, but just my personal interpretation. > > Since Jakarta Authentication would need to do the latter, we decided > not to introduce new generics for Authentication in Jakarta EE 9. > > Kind regards, > Arjan
I agree with Bill's earlier assessment.
There were too many variables to open this door for Jakarta EE 9.
The base Jakarta EE 9 release plan would not support the introduction
of Generics into the APIs. If a Project desired to introduce Generics,
they would be required to create their own Release Plan.
> > 2. Whether spec-defined properties
should move from javax. to > jakarta.* (along w/ packages) > Yes, definitely.
> 3. Whether the targetNamespace
for the Batch XML / XSD needs to > change (currently using targetNamespace="http://xmlns.jcp.org/xml/ > ns/javaee%22) > Yes, definitely. I don't
think we've decided on the new base > namespace yet; we're waiting for advice from Eclipse.
+1, agree. Need to move on
this with Eclipse...
> > But I don't see any of this here: https://eclipse-ee4j.github.io/ > jakartaee-platform/jakartaee9/JakartaEE9ReleasePlan > Seems like we need to start
Just for completeness, the other
item we agreed to allow was the use of @Repeatable for those cases where
it was missed during earlier Java EE releases.
Will generate the FAQ and send out
a PR shortly...
> > Now... if these three items are still under discussion then I can
> dig through the various threads... I'm not asking anyone to go > collect links for me. > > But I'm just asking in case maybe there already is a consensus > captured somewhere and I'm just not looking in the right place...
> and/or maybe that "release plan" doc just needs to be updated? > > If that's the doc that needs to be updated can someone please point
> me to the repo to open the issue on? > My answers above are from memory,
so they might not be perfect. > Filing these as issues in the platform project is one way to record
> the decisions, but I think people would find it easier to find the
> answers to their questions if we started a FAQ. > _______________________________________________ > jakartaee-platform-dev mailing list > jakartaee-platform-dev@xxxxxxxxxxx > To unsubscribe from this list, visit https://www.eclipse.org/ > mailman/listinfo/jakartaee-platform-dev