-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: Linux
I have a bunch of Maven2 projects that depend on each other, each built separately
by Hudson. Before we upgraded to 1.318 and selected "Use private Maven repository"
for these projects, they correctly found their upstream/downstream dependencies
and built in the right order. Now, a change to any one project only builds it.
I have an aggregation project that runs (sonar, findbugs, pmd etc) on a top-level
pom over all these projects, also with a private Maven repository, and it
correctly identifies modules and kicks off dependent builds (although I'd rather
it didn't!), so the fact that the sub-modules don't is a bit strange.
Couple questions - which version of Hudson had you upgraded from? 1.317 or
earlier? Were you using the private Maven repos before upgrading to 1.318? (The
description phrasing isn't entirely clear on this) The aggregation project - are
you saying that it's kicking off the non-aggregate projects as downstream
builds? Could you give me a quick sense of how your projects (the individual
projects and the aggregate project) are set up, in re: top-level/modules and
intended upstream/downstream relationships? I've got a feeling this involves
fingerprints for the build artifacts getting confused, but I'm not entirely sure.