I'd really like to hear from whoever will lead the "Jakarta CDI"
project when it is created. My understanding is that there are
things that CDI would like to change in DI, and so my suggestion was
that the CDI team take over DI as well, and possibly incorporate it
into the CDI spec in the future.
For now, we could just fork it and add it as a separate repository
under the (to be created) CDI project, and add it as a second spec
that the CDI project would produce. Since the spec is just
javadocs, that should trivial.
All this is dependent on the outcome of the Red Hat discussion, of
course.
Wayne Beaton wrote on 6/12/19 8:02 PM:
Right. I recall that thread now.
Is this a "stable API". i.e. can we just add it to "Eclipse
Project for Jakarta Stable APIs"?
If it needs to be a separate project, then we'll need
somebody to author a project proposal.
Wayne
The last statement on Dependency Injection was from Bill
saying that he talked to one of the spec leads and they were
not interested in moving it over to Eclipse. There was a
suggestion to fork it and have Red Hat take ownership. We
are discussing that.
It only has 6 classes, no spec text and everything is
licensed under the Apache License.
What would it take to create a fork of this project at
Eclipse?
We didn't get to this agenda item on
the call today.
We have a handful of "missing" specifications
that need to be dealt with for Jakarta EE 8.
Here's the status for a few of them:
We have a proposal for Jakarta
Contexts and Dependency Injection.
The proposal is in our system, but has not been
opened for community review (the page is access
restricted while in this draft mode). The usual
process is that the project team connects with
EMO to request that we open it for review. EMO
is ready to go when that happens.
I do not know the status of Dependency
Injection. Does anybody have any
insight/status on this?
We have the proposal for Jakarta Bean
Validation open for community
review. I will start the Specification Committee
ballot. Watch your inboxes.
The Jakarta Server Faces APIs are
part of Eclipse Mojarra. The plan is to we leave
them there and create a new specification
project (which I'm tracking via this
GitHub Issue). Over time, the APIs will be
moved to the specification project. Or they
won't. It'll be up the community.
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
