I have a situation where I have two Upsource projects, each with a maven build; the first is for our common libraries and the second depends on those common libraries. I am having an issue where the second project cannot find its dependencies from the first project when being analyzed by Upsource, even though that first project has been set up and analyzed by Upsource.
Looking through the maven repository that gets built by Upsource (<Upsource Home>/temp/upsource-analyzer/upsource-tmp/m2repo/) I notice that the jars from the common project are not there, even after the project has been analyzed (though the dependencies used for that build are). I've tried deleting and recreating the project a number of times as well as deleting the Upsource maven repository, all with no luck. I have the same setup in TeamCity which works fine and building the projects locally works fine as well. However, in both of those cases, I know that the associated maven repositories are getting updated properly with the contents of the required common libraries.
My questions are:
- Should the jars from the common project get put into the Upsource maven repository?
- Am I just going about this in the wrong way? I am starting to wonder if there is just a better way to handle dependencies between projects, any advice would be welcome.