On Wed, Mar 4, 2009 at 2:12 PM, Wendy Smoak <[email protected]> wrote:
> On Wed, Mar 4, 2009 at 3:06 PM, David C. Hicks <[email protected]> wrote: > > I'm trying to run release:prepare on my project. There are to modules in > > the project that other modules depend on. The project builds just fine. > > The problem seems to be that release:prepare does not do an "install" on > > the modules, so those dependent modules cannot find the artifacts in the > > repository. How does one get around this problem? Is there some way to > > force release:prepare to install the artifacts that it builds? > > It should find them in the reactor, but in some cases it doesn't (or > maybe can't -- not sure if this is a bug or just the way it has to > be.) I'd say it "works as designed". I think the reasoning behind not running the install goal by default is that at the time that version isn't released yet, so it shouldn't be installed (the release may fail later, which would incorrectly leave artifacts with that version in your local repository). It'll work if you use straight-up reactor dependencies, but will fail for example if you use dependency:copy somewhere in the same build (in which case you need to add install as a preparationGoal). Kalle
