[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18654: ------------------------------------ {quote}there is a Maven plugin for that{quote} Yes: https://maven.apache.org/plugins/maven-jdeps-plugin/ So, I've added a jdeps profile to the parent pom for version 4.5.2.AM3-SNAPSHOT. https://github.com/jbosstools/jbosstools-build/commit/4821b55ddc14247a525... Now, you can build any jbosstools-* project like this... 1. Create a toolchains.xml file that looks like this, ideally in your ~/.m2 folder: {code}<?xml version="1.0" encoding="UTF8"?> <toolchains> <toolchain> <type>jdk</type> <provides> <version>1.8</version> <vendor>openjdk</vendor> </provides> <configuration> <jdkHome>/usr/lib/jvm/java-1.8.0-openjdk/</jdkHome> </configuration> </toolchain> <toolchain> <type>jdk</type> <provides> <version>9</version> <vendor>openjdk</vendor> </provides> <configuration> <jdkHome>/usr/lib/jvm/java-9-openjdk/</jdkHome> </configuration> </toolchain> </toolchains>{code} 2. Update to latest parent pom: {code} cd /path/to/jbosstools-openshift sed -i -e "s/4.5.2.AM1-SNAPSHOT/4.5.2.AM3-SNAPSHOT/" pom.xml # grab parent pom 4.5.2.AM3-SNAPSHOT {code} 3. Run {code} mvn clean install -Pjdeps -Djdeps-jdk-version=1.8 -Djdeps-jdk-vendor=openjdk --global-toolchains ~/.m2/toolchains.xml # or mvn clean install -Pjdeps -Djdeps-jdk-version=9 -Djdeps-jdk-vendor=openjdk --global-toolchains ~/.m2/toolchains.xml {code} We could also set up Jenkins jobs to do these checks, if we wanted. WDYT, [~mmalina] [~psrna] [~jeffmaury] [~rob.stryker] -- This message was sent by Atlassian JIRA (v7.5.0#75005)