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
[WFCORE-5861] Fix InaccessibleObjectException with OpenJDK17 and embed-server #5050
Conversation
…nt.jar so it can embed the server on SE 16+ Configure the settings in properties in the root pom so they can be shared between the bootable-jar/boot/pom.xml and the cli/pom.xml
Core - Full Integration Build 11300 outcome was FAILURE using a merge of 4dcd707 |
Core - Full Integration Build 11433 outcome was UNKNOWN using a merge of 4dcd707 Failed tests
|
Core - Full Integration Build 11434 outcome was FAILURE using a merge of 41265df Failed tests
|
Core - Full Integration Build 11435 outcome was FAILURE using a merge of 41265df Failed tests
|
Core - Full Integration Build 11436 outcome was FAILURE using a merge of 41265df |
/retest |
1 similar comment
/retest |
Core - Full Integration Build 11304 outcome was FAILURE using a merge of 41265df |
…r CLI client launching an embedded server Jira Issue: https://issues.redhat.com/browse/WFCORE-5861
Core - Full Integration Build 11307 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11444 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11437 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11301 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11445 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11309 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11446 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11310 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11308 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11447 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11448 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11311 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11313 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11450 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11314 outcome was FAILURE using a merge of c91d78f |
Core - Full Integration Build 11451 outcome was FAILURE using a merge of c91d78f |
/retest |
Core - Full Integration Build 11315 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11454 outcome was UNKNOWN using a merge of c91d78f Failed tests
|
/retest |
Core - Full Integration Build 11461 outcome was FAILURE using a merge of c91d78f Failed tests
|
Core - Full Integration Build 11465 outcome was FAILURE using a merge of c91d78f Failed tests
|
Tests pass locally by using the default maven local repository, however, Team City CI explicitly uses the non-default maven local repo. That's an issue when we are using the jboss-client.jar; we need to specify the location of the maven repo to be able to run the embedded server. Closing this in favor of https://issues.redhat.com/browse/WFCORE-5873 |
It builds on top of #5028, it adds a test case to verify it.
Jira issue: https://issues.redhat.com/browse/WFCORE-5861