Workaround Groovy conflicts in Debug examples as daily build is failing #1196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes 2 things that are causing daily build failing, both are related:
Caused by: groovy.lang.GroovyRuntimeException: Conflicting module versions. Module [groovy-xml is loaded in version 4.0.22 and you are trying to load version 4.0.16
Every now and then we run into a situation when Groovy version is conflicting. It cannot be avoided when Quarkus QE Test Framework is build with a different version than used in tests. In past it happened as well and I simply disabled tests, but lately they were enabled here #1134 because the test worked. We are likely to run into this again so I suggest to avoid Groovy
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:3.3.0:integration-test (default) on project examples-debug: Execution default of goal org.apache.maven.plugins:maven-failsafe-plugin:3.3.0:integration-test failed: A required class was missing while executing org.apache.maven.plugins:maven-failsafe-plugin:3.3.0:integration-test: org/apache/commons/io/FileUtils
No idea why it sometimes happen (happened to me thrice when I tried to fix the Groovy thingy), but it's easy to avoid by simply dropping Apache Utils from surefire debug provider
Please check the relevant options
run tests
phrase in comment)Checklist: