Paul Gooderham
Paul Gooderham
The process to run the binary scanner acceptance test is expressed in the script liberty-maven-plugin/src/it/binary-scanner-it/run-binary-scanner-it. This could be rewritten to run on command as a github action.
Multiline replacements must be restructured to work on Windows. Also, EE9 should not be used on LMP 3.6 so this test case should use EE8 in the umbrella tests.
Currently the binary scanner produces an invalid argument exception when we pass invalid version numbers like Jakarta EE 12. We should have a specialized exception to report this situation as...
In the dev-it bucket the tests wait for dev mode to start using the line: ``` verifyLogMessageExists("Liberty is running in dev mode." ``` Unfortunately after dev mode prints this message...
When the server starts with no features and the app is not deployed then adding features can fail at times. Start with the demo-devmode project and remove all features from...
Use the project guide-maven-multimodules and add SystemLivenessCheck.java to the ear module. Also add JavaEE 8.0 and MicroProfile 4.1 to the ear/pom.xml. Start devmode with `mvn liberty:devc -DhotTests` on a *Linux*...
After initiating a rebuild due to the build file being updated generate features should run but it should generate the same features. This can be detected in the console log...
This test started to fail after the change not to write the generated-features.xml file in generate features mojo if the file has not changed. This test uses -DrecompileDependencies=false and -DhotTests=true....
After adding a new Java file the endpoint is not visible. Tested on Linux. First start with a kernel image: kernel-slim-java8-openj9-ubi. Using the demo-devmode project add a command to Dockerfile...
When you add webProfile-7.0 to server.xml you expect to see message #1. Generate Features is called twice and the error message appears twice. Details below. ``` [INFO] Running liberty:generate-features [ERROR]...