We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are already banning several other org.jboss.spec.javax.* specs and I wonder whether we should also ban org.jboss.spec.javax.el:*.
org.jboss.spec.javax.*
org.jboss.spec.javax.el:*
For the record, in Quarkus 2.2.5 it used to be pulled via (not sure about the current master)
No response
uname -a
ver
java -version
mvnw --version
gradlew --version
The text was updated successfully, but these errors were encountered:
cc @gsmet @maxandersen @aloubyansky
Sorry, something went wrong.
Ban org.jboss.spec.javax.el:jboss-el-api_3.0_spec
cfba382
Fixes quarkusio#24442
gsmet
Successfully merging a pull request may close this issue.
Describe the bug
We are already banning several other
org.jboss.spec.javax.*
specs and I wonder whether we should also banorg.jboss.spec.javax.el:*
.For the record, in Quarkus 2.2.5 it used to be pulled via (not sure about the current master)
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: