[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-community] Fork Eclipse MicroProfile Configuration as Jakarta Configuration.
|
Because none of the JSR330 spec leads responded in any form. There
clearly is a discussion going on here. When we had the MP pull vote it
was clearly stated that how Jakarta consumed MP specs was to be
defined on the Jakarta side. That is happening now. Why is it a
surprise that there is not a unanimous opinion?
On Mon, Apr 6, 2020 at 6:23 AM <werner.keil@xxxxxxxxx> wrote:
>
> This sounds totally hypocritic because you (Red Hat) did just that with JSR 330 when the contributors and Spec Leads were unwilling to contribute to Jakarta EE, so RH (Scott) forked it into Jakarta Inject Based on the mentioned ASLv2 allowing it.
>
>
>
> There is currently no evidence Google, Square or any of the other users of the Guice community are adopting Jakarta Inject, so it is just a fork whether anybody touches those old annotations or not.
>
>
>
> So why did you do it for Inject and say this should not be done with MP or the fork that already was done with JSR 382?
>
>
>
> Werner
>
