CircleCI should use dependent Maven artifacts from same repository


#1

CircleCI is trying to resolve an internal build artifact from a server, instead of using the “previously” build.

Long story:
I have tested CircleCI to build the Apache Incubator ODF Toolkit project using Maven.
There is a git repository with directories on the same level, both containing a pom.xml, but one is depending on the other.
If the build would not break - as the snapshot JAR is not on the Apache Nexus - I would not have noticed that CircleCI is not using my current sources, but resolving to an outdated dependency.
Seems there is a little too much parallelization going on in the background…

Those errors might take developers hours, as they are hard to find…

PS: A general stretch goal would be to parse the Maven output and condense it to relevant high level information :wink:


#2