Either refactor your build so that it retrieves these artifacts from the reactor (this is a good plan anyway... for example replace dependency:copy with dependecy:copy-dependencies, etc)
Or (if you cannot refactor... maybe one of the plugins you are using is not written to check the reactor for artifacts) change the preparationGoals in the release plugin config from "clean verify" to "clean install" Note: if you have to change to "clean install" that indicates subtle issues with your build... life is better if you can move to "clean verify" (but it's not the end of the work if you cannot) -Stephen 2009/3/4 David C. Hicks <[email protected]> > I'm sure there's got to be some little something that I'm missing. > > 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? > > Thanks, > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
