-
Bug
-
Resolution: Done
-
Major
-
27.0.0.Alpha5
-
None
I've been trying to verify the PoC presented by this commit from this branch, but no success by now.
I was testing the baremetal part only, the provided Helm Charts were not tested yet. As we agreed, the WildFly Maven plugin should be used for this purposes, so the bootable-jar-openshift profile makes no sense in QS pom.xml file.
Firstly I was trying to run the integrated ToDoIT.java test by executing the mvn clean verify -Parq-managed command, but it failed on resolving necessary expressions. Do I miss something or the pom.xml lacks some additional configuration?
Secondly, I was trying to pre-build a server with mvn clean verify -Popenshift command and run it as a separate process and then run a mvn clean verify -Parq-remote. The jbossHome property in arquilian.xml has been set to a pre-built server folder. Still no success.
All of these steps have been made by following the instructions in pom.xml. The Readme instructions obviously are outdated (bootable jar part, etc). The QS itself needs an update due to the JakartaEE migration, at the moment it fires this exception.
Is that an issue or do I miss some details?
- incorporates
-
WFLY-17185 todo-backend QS fires a StrictJpaComplianceViolation exception
- Closed
- is caused by
-
JBEAP-23975 todo-backend QS fires a StrictJpaComplianceViolation exception
- Closed