Skip tests in intermediate build steps to fix Linux port conflict#100
Merged
Skip tests in intermediate build steps to fix Linux port conflict#100
Conversation
Set skipTests=true in the parent POM so all modules skip tests by default, and override it to false in pom-step-05.xml where tests should run. This fixes the build failure on Linux where running tests in intermediate step modules (step-02, step-03) caused MariaDB port conflicts when step-04 tried to start its demo database on port 33328. Co-authored-by: dkayiwa <1390773+dkayiwa@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix errors from running mvn clean install
Skip tests in intermediate build steps to fix Linux port conflict
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
mvn clean installfails on Linux because surefire tests run in step-02/step-03 modules, starting/stopping MariaDB on port 33126 while the mariaDB4j maven plugin has an instance on port 33326. This causes port 33328 to be unavailable when step-04 tries to start its demo database.skipTests=truein the parent POM so all modules skip tests by defaultskipTests=falseinpom-step-05.xml, which is the only module with explicit surefire configurationTests now run exactly once (in step-05) instead of redundantly in every jar-packaged module, eliminating the MariaDB process interference.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
mavenrepo.openmrs.org/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.12/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.12/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.12 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.12/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/openmrs-standalone/openmrs-standalone org.codehaus.plexus.classworlds.launcher.Launcher clean install -pl .(dns block)/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.12/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.12/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.12 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.12/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/openmrs-standalone/openmrs-standalone org.codehaus.plexus.classworlds.launcher.Launcher clean compile -f pom-step-05.xml(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.