Re: [jakarta.ee-spec.committee] Faces and Validation and CDI oh my

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

+1

By way of expectation management, the process requires two weeks of community review and one week of creation review for new project proposals. We decided some time ago that we can overlap these (and can do the specification committee vote in parallel). But I still need at least two weeks from when EMO is told "go".

Wayne

On Thu, Jun 13, 2019 at 12:25 PM Scott Stark <sstark@xxxxxxxxxx> wrote:

The Jakarta CDI proposal is pending. We can move DI into that project for now.

On Jun 12, 2019, at 11:02 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

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.

https://www.eclipse.org/projects/handbook/#starting

Wayne

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.