-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
ArC: initial implementation of CDI Build Compatible Extensions #31444
ArC: initial implementation of CDI Build Compatible Extensions #31444
Conversation
@@ -987,8 +987,13 @@ Builder disposer(DisposerInfo disposer) { | |||
return this; | |||
} | |||
|
|||
/** | |||
* @deprecated use {@link #alternative(boolean)} and {@link #priority(Integer)}; | |||
* this method will be removed at some time after Quarkus 3.6 |
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.
Quarkus 3.6??
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'm thinking roughly 6 months after the Quarkus release in which this would happen, which is 3.0. Given our roughly monthly release cadence, that's 3.6. Do you have another preference?
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'd say that Deprecated.forRemoval()=true
is enough - BeanInfo.Builder.alternativePriority(Integer)
is not part of the public API.
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.
Added @Deprecated(forRemoval = true, since = "3.0")
.
@@ -201,12 +201,22 @@ public THIS targetPackageName(String name) { | |||
return self(); | |||
} | |||
|
|||
/** | |||
* @deprecated use {@link #alternative(boolean)} and {@link #priority(int)}; | |||
* this method will be removed at some time after Quarkus 3.6 |
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 would recommend to rather use since = "3.0"
in the @Deprecated
annotation.
We never really give estimate of when something will be removed. But us knowing when it was removed is useful for knowing when it's relatively safe to remove something.
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.
We actually often do that in ArC, but adding since
is a great point, I'll do that.
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.
+1 for since
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.
Added @Deprecated(forRemoval = true, since = "3.0")
.
e98a374
to
75a8e79
Compare
Added |
This comment has been minimized.
This comment has been minimized.
75a8e79
to
8c7c1ce
Compare
Made the changes we discussed earlier today. One thing I forgot: I'd appreciate a second pair of eyes on the changes to
Maybe I should replace this code with synthetic injection points, as introduced recently. That might simplify things a lot, though I'm not sure it fully implements all the peculiarities of looking up a "current" injection point. |
This comment has been minimized.
This comment has been minimized.
+1
What peculiarities do you have in mind? You can take a look at the SyntheticInjectionPointMetadataTest and SyntheticInjectionPointMetadataInvalidTest to see what's tested (hence supported ;-). |
8c7c1ce
to
50d4034
Compare
Rebased to avoid the failures. After offline discussion, I left |
This comment has been minimized.
This comment has been minimized.
Failing Jobs - Building 50d4034
Full information is available in the Build summary check run. Failures⚙️ Native Tests - Misc4 #- Failing: integration-tests/opentelemetry-jdbc-instrumentation
📦 integration-tests/opentelemetry-jdbc-instrumentation✖
|
The
The exact same failure seems to occur on a bunch of other PRs: https://github.com/quarkusio/quarkus/pulls?q=is%3Apr+PostgresOpenTelemetryJdbcInstrumentationIT+testPostgreSqlQueryTraced Gonna merge this. |
Related to #28558
Vast majority of changes are additions that are pretty well isolated. To review, it's probably best to focus on changes to already existing files.
I plan to submit another PR with additions of the CDI TCK runner modules, as this PR is huge already.