Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Compatible Extensions Proposal #452

Closed
manovotn opened this issue Sep 17, 2020 · 1 comment
Closed

Build Compatible Extensions Proposal #452

manovotn opened this issue Sep 17, 2020 · 1 comment
Labels
Lite Related to CDI Lite lite-extension-api Issues related to CDI Lite extension API proposal

Comments

@manovotn
Copy link
Contributor

TL;DR

Blog post you should read - www.cdi-spec.org/news/2020/09/15/CDI_Lite_extension/
PR with API proposal - #451
For hands-on playing with API, use this fork - https://github.com/Ladicek/quarkus-fork/tree/experiment-cdi-lite-ext

What is this

This is a proposal on how Build Compatible Extensions ( e.g. CDI Lite extensions) could look like. Various discussions in the past showed that regardless of what would CDI Lite look like, it will need some form of extensions because the existing ones are not suitable for build-time and extension are an important factor for integration of various frameworks.

This issue and the PR linked to it (#451) come with a WIP proposition that we would like to gather feedback on.

There is a blog post on CDI website that you should check out. It goes deeper into what Build Compatible Extensions Proposal is and how it works. Please do give it a read.

What it isn't

This proposal does not aim to cover what CDI Lite should/shouldn't contain and focuses solely on how could the Lite extension API look like.

How can I play with this new API

The linked PR gives you a glimpse of what the API draft looks like right now. However, that's just API - it's nice but you cannot try it out in action, right?

That's why we have also created a simple implementation for the annotation transformation part of API inside Quarkus. It uses none of Quarkus-specific APIs, just what we presented here and having tried that in Quarkus proves its viability for build-time environments (although it doesn't limit it for just that). For the sake of simplicity it right now contains a copy of the APIs inside the fork.

Intructions on how to try it out are in the blog post.

How to provide feedback

Got an idea how to improve it? What's missing or what's superfluous? We'd love to hear what you think of this API!
In order to keep it all in a readable and traceable format, please provide your feedback in form of separate GH issue on this repo with label lite-extension-api.

@manovotn manovotn added the lite-extension-api Issues related to CDI Lite extension API proposal label Sep 17, 2020
@Ladicek
Copy link
Contributor

Ladicek commented Oct 21, 2021

Let's close this -- the extension API is now done and merged.

@Ladicek Ladicek closed this as completed Oct 21, 2021
@Ladicek Ladicek added the Lite Related to CDI Lite label Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lite Related to CDI Lite lite-extension-api Issues related to CDI Lite extension API proposal
Projects
None yet
Development

No branches or pull requests

2 participants