Folks, you should wait with submitting PRs until next week. Contributions cannot be random, there is no anarchy, we should follow the plan. The main goal is releasing the first version of EE4J asap. It must be Java EE 8 compatible. It means no API changes. We (PMC) are working on defining some general rules for all sub-projects such us which branch goes to release, where new version development should be done, etc. We haven’t put this plan on paper yet because there are some open issues. I expect that it will be done on the next PMC meeting. I’ll keep you updated. I see a lot of energy here, it needs to be applied in the right direction.
Thanks, Dmitry
Super news! :)
I hope we can start work on evolving the API soon.
My two initial proposals would be to further align with CDI and to define support for the existing javax.annotation.security.RolesAllowed annotation (several JAX-RS implementations already support that in a proprietary way, and MicroProfile JWT-AUTH defines this for JAX-RS as well).
Kind regards, Arjan Tijms
_______________________________________________ ee4j-community mailing list ee4j-community@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community
|
