-
Notifications
You must be signed in to change notification settings - Fork 85
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
Explicitly set java version as a query parameter in the java-quarkus zip urls #366
Conversation
Hi @vinokurig. Thanks for your PR. I'm waiting for a devfile member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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 if java 17 is the default for the images.
Is there a reason not using 21 by default here?
The |
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.
unrelated to java version
@maxandersen do we need -Djava.util.logging.manager=org.jboss.logmanager.LogManager
arg in the commands?
ould not load Logmanager "org.jboss.logmanager.LogManager"
java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239)
at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:222)
at java.logging/java.util.logging.Logger.demandLogger(Logger.java:649)
at java.logging/java.util.logging.Logger.getLogger(Logger.java:718)
at java.logging/java.util.logging.Logger.getLogger(Logger.java:702)
at com.google.inject.internal.util.Stopwatch.<clinit>(Stopwatch.java:27)
at com.google.inject.internal.InternalInjectorCreator.<init>(InternalInjectorCreator.java:62)
at com.google.inject.Guice.createInjector(Guice.java:87)
at com.google.inject.Guice.createInjector(Guice.java:69)
at com.google.inject.Guice.createInjector(Guice.java:59)
at org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
at org.codehaus.plexus.DefaultPlexusContainer.<init>(DefaultPlexusContainer.java:206)
at org.apache.maven.cli.MavenCli.container(MavenCli.java:651)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:196)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
[INFO] Scanning for projects...
[INFO]
In the pom file? Yes. That should not give such error. When does that happen? |
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 good to go with 17 as rhbq don't default to 21 yet.
@michael-valdron Could you please merge if you don't have any objections. |
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 to follow versioning I'd suggest the following:
- Create patch version copies with the PR changes:
1.3.1
1.4.1
- Deprecate the base versions that are broken by adding the
Deprecated
tag:
See deprecation example.
This also mean |
Done |
d199636
to
fe623c9
Compare
/ok-to-test |
/retest |
a2284ee
to
98aceab
Compare
…zip urls Signed-off-by: ivinokur <ivinokur@redhat.com>
@michael-valdron do you have an idea why the tests are failing? |
The odo v2 failure is an ongoing issue we are tracking: devfile/api#1514 The odo v3 failure seems to be triggerred by test case failures on the
In fact, almost looks like it could be the same issue causing devfile/api#1514:
I'll open an issue to investigate this one as well. #369 will temporarily skip odo testing on |
Opened an issue tied to odo v3 test failures: devfile/api#1533 FYI @vinokurig |
@michael-valdron Thank you for the explanation, can we proceed with current changes? |
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.
@michael-valdron Could you please merge? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ibuziuk, maxandersen, michael-valdron, vinokurig The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Child sample works with these changes to parent: |
What does this PR do?:
Explicitly set java version in the java-quarkus zip urls to java 17, in order to fix the error from the
init-compile
command:Which issue(s) this PR fixes:
N/A
PR acceptance criteria:
Have you read the devfile registry contributing guide and followed its instructions?
Does this repository's tests pass with your changes?
Does any documentation need to be updated with your changes?
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)
How to test changes / Special notes to the reviewer: