Until all the projects are updated to build cleanly with the new
Photon-based dependencies (like Red Deer 2.1 instead of 2.0 and Eclipse 4.8
instead of 4.7.3a), and have built in Jenkins, you'll have to build the
whole set of projects locally in order to build a downstream one like
jbosstools-central.
As you can see from the root pom [1], Central depends on several upstream
projects:
base, server, javaee, portlet (?), jst, hibernate, vpe.
[1]
https://github.com/jbosstools/jbosstools-central/blob/master/pom.xml#L27-L62
Once you've built the upstream projects locally (using `mvn clean install
-DskipTests if you're in a hurry), you can then pass those urls to the
downstream builds with
-Djbosstools-server-site=file:///path/to/jbosstools-server/site/target/repository/
You could also build using the older parent pom, version
4.7.3.Final-SNAPSHOT, but then pass in these variables to ensure you're
using the correct TP and will be correctly nagged about version bumps where
needed:
-DTARGET_PLATFORM_VERSION_MIN=4.71.1.Final
-DTARGET_PLATFORM_VERSION_MAX=4.73.1.Final
-DTARGET_PLATFORM_CENTRAL_MAX=4.73.0.Final-SNAPSHOT
-DBUILD_ALIAS=AM1
Hope that helps!
Meanwhile, base, forge, fuse extras, and the openshift restclient are
*green*. Let's get the rest fixed ASAP!
[2]
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt /
http://nick.divbyzero.com
<
https://red.ht/sig>
TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
@ @redhatnews <
https://twitter.com/redhatnews> Red Hat
<
https://www.facebook.com/RedHatInc>
<
https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus