On Thursday 05 March 2009 David C. Hicks wrote: > Todd Thiessen wrote: > > However, when you have dependencies between modules, the release > > prepare will fail by default since it doesn't do an install. Without an > > install, one module doesn't have access to the artifacts of another. > > To be completely fair, I just realized, reading this, that there is a > little twist. In my case, the two modules that are missing are modules > of a module. I don't think it should make any difference, but maybe > there is a defect that begins at the 3rd level. Again, here's a bit of > a skeleton view: > > Project > ModuleA(pom) > ModuleA1(pom) > ModuleA2(pom) > ModuleB(jar, depends on ModuleA1,ModuleA2) > > When it gets to ModuleB, the failure is in finding either of those two > dependencies.
How did you define the dependencies in ModuleB? Did you specify the correct type (pom) for the dependencies? - martin
signature.asc
Description: This is a digitally signed message part.
