It's totally an issue of mine I made in this commit
https://github.com/mickaelistria/jbosstools-build/commit/07bf148db08f0c14d5a67d98aaa102d9e0df473b
, which was part of work for https://issues.jboss.org/browse/JBIDE-13014
. It has just been fixed in this commit:
https://github.com/jbosstools/jbosstools-build/commit/7a9228fe83d2beed09b0a2e982df0ab0525df8f1
.
You should be able to build locally by fetching the latest version
of parent pom, and "mvn install" it.
When build #202 of job
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-4.0_trunk.parent/
is done, you can expect CI builds to be back to a normal state.