Do I understand it correctly, that any pom.xml analysis has been dropped and has never got resurrected? Is there a chance to have it back? Otherwise the whole CI idea stops making sense for our maven-pom-based-huge-dependency-tree projects, as if an updated library snapshot does not trigger re-building all the gazillion applications which depend on this snapshot, automatic CI just stops working, as one needs to 1) know, which apps depend on which lib, 2) go through all of them and click "run" to trigger re-building. And, "no", referencing repositories to watch and trigger the build on commit won't work either. Neither does scheduled builds, just because of too many projects and interdependencies. Jenkins has this very proper pom-based dependency analysis which works very well. Having this in QB would be amazing too.