as asked on jbosstools-dev mailing list

copy of the mail content from Nick:

I've added a jdeps profile to the parent pom for version 4.5.2.AM3-SNAPSHOT.

https://github.com/jbosstools/jbosstools-build/commit/4821b55ddc14247a5254699bc023e8d6fa368718

Now, you can build any jbosstools-* project like this...

1. Create a toolchains.xml file that looks like this, ideally in your ~/.m2 folder:

<?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>
2. Update to latest parent pom:

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
3. Run

mvn clean install -Pjdeps -Djdeps-jdk-version=1.8 -Djdeps-jdk-vendor=openjdk --global-toolchains ~/.m2/toolchains.xml

1. or
   mvn clean install -Pjdeps -Djdeps-jdk-version=9 -Djdeps-jdk-vendor=openjdk --global-toolchains ~/.m2/toolchains.xml
   We could also set up Jenkins jobs to do these checks, if we wanted.

Please take some time to run your builds with the jdeps profile enabled, and see what tests (or compilation) breaks.

You may also want to use the -P maximum profile to see what happens when you build using the latest Oxygen.2.RC2 bits.

Net week after we declare AM2 complete, I'll pull another TP update to get the Oxygen.2.RC4/GA bits.