-
Notifications
You must be signed in to change notification settings - Fork 48
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
WELD-2769 Support the ELAwareBeanManager #182
Conversation
JIRA link - https://issues.redhat.com/browse/WELD-2769 |
<groupId>jakarta.enterprise</groupId> | ||
<artifactId>jakarta.enterprise.cdi-el-api</artifactId> | ||
<version>${cdi.api.version}</version> | ||
</dependency> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'll also need to add an exclusion for EL API artifact here.
I'll check and add on to your PR if needed.
Signed-off-by: Arjan Tijms <[email protected]>
bfec2c8
to
81d809d
Compare
Thanks @arjantijms! |
Thank you too! Next step would be updating weld-api in weld core, and then having |
Yes, we need Weld API release for that but I am waiting on how the method invokers PR turns out. |
I've gone ahead and released the API so that this doesn't get forgotten. Here's the PR upgrading the API and making |
No description provided.