-
Notifications
You must be signed in to change notification settings - Fork 61
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
Bump quarkus.version from 1.13.7.Final to 2.0.0.Final #253
Conversation
Bumps `quarkus.version` from 1.13.7.Final to 2.0.0.Final. Updates `quarkus-bom` from 1.13.7.Final to 2.0.0.Final - [Release notes](https://github.com/quarkusio/quarkus/releases) - [Commits](quarkusio/quarkus@1.13.7.Final...2.0.0.Final) Updates `quarkus-maven-plugin` from 1.13.7.Final to 2.0.0.Final Updates `quarkus-bootstrap-maven-plugin` from 1.13.7.Final to 2.0.0.Final --- updated-dependencies: - dependency-name: io.quarkus:quarkus-bom dependency-type: direct:production update-type: version-update:semver-major - dependency-name: io.quarkus:quarkus-maven-plugin dependency-type: direct:production update-type: version-update:semver-major - dependency-name: io.quarkus:quarkus-bootstrap-maven-plugin dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
@shumonsharif crap we have to work on native to fix quakus 2.0 release: https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.0 Error: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected an instance of Random/SplittableRandom class in the image heap. Instances created during image generation have cached seed values and don't behave as expected. To see how this object got instantiated use --trace-object-instantiation=java.util.Random. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=. Or you can write your own initialization methods and call them explicitly from your main entry point. com.oracle.svm.core.util.UserError$UserException: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected an instance of Random/SplittableRandom class in the image heap. Instances created during image generation have cached seed values and don't behave as expected. To see how this object got instantiated use --trace-object-instantiation=java.util.Random. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=. Or you can write your own initialization methods and call them explicitly from your main entry point.
Caused by: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected an instance of Random/SplittableRandom class in the image heap. Instances created during image generation have cached seed values and don't behave as expected. To see how this object got instantiated use --trace-object-instantiation=java.util.Random. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=. Or you can write your own initialization methods and call them explicitly from your main entry point.
Caused by: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected an instance of Random/SplittableRandom class in the image heap. Instances created during image generation have cached seed values and don't behave as expected. To see how this object got instantiated use --trace-object-instantiation=java.util.Random. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=. Or you can write your own initialization methods and call them explicitly from your main entry point. |
@dufoli some interesting results for this PR ... Local build with GraalVM CE 21.0.0 (build 11.0.10+8-jvmci-21.0-b06) - PASS I don't know if delaying ClientImpl to runtime is the right approach for this ... because we'll have to add a whole load of CXF classes to the delayed list? |
@shumonsharif agreed, I just want to test. quarkusio/quarkus#14904 |
I will reopen an issue link to this one. I found that quarkus do runtime init class to fix that on all extension: the goal is to have seed set at runtime to avoid fake random. |
cd17809
to
7f64caa
Compare
Bumps
quarkus.version
from 1.13.7.Final to 2.0.0.Final.Updates
quarkus-bom
from 1.13.7.Final to 2.0.0.FinalRelease notes
Sourced from quarkus-bom's releases.
... (truncated)
Commits
ca1e69e
[RELEASE] - Bump version to 2.0.0.Final7cd1dff
Fix Gradle repository URLbab5dfd
CLI: doc/help update; correct -P parsing1bbbe60
Fix dev mode compile issues8cdda6b
Merge pull request #18090 from gsmet/2.0.0.final-backports-678a9136
H2 DevServices should not attempt to stop a stopped server4e23423
Validate option for hibernate database generationdb377c3
Disable AvailableSettings.HBM2DDL_SCRIPTS_CREATE_APPENDc507390
Upgrade to Hibernate ORM 5.5.3.Finaledc9daa
Provide actionable message when@QuarkusIntegrationTest
is run before the Qua...Updates
quarkus-maven-plugin
from 1.13.7.Final to 2.0.0.FinalUpdates
quarkus-bootstrap-maven-plugin
from 1.13.7.Final to 2.0.0.FinalDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)