Before your CI system runs your project, you can run this cmd "svn up and mvn install" .This may will help you?
On Tue, Apr 14, 2009 at 1:41 AM, David Hoffer <[email protected]> wrote: > More details. > > It turns out the CI system just did a deploy; instead of clean deploy which > works. > > We aren't clear why the clean is necessary because the CI system is doing a > full checkout into clean directory. We thought clean just removed the > target folders. > > Any insight? We would like to know why this works. > > -Dave > > On Mon, Apr 13, 2009 at 11:28 AM, David Hoffer <[email protected]> wrote: > > > I have a multi-module maven project that works fine on developer systems, > > however fails on CI builds. We aren't sure why but the error log > indicates > > that certain modules cannot find recent code added to other modules. So > it > > seems that maven might be using a prior snapshot instead of the new > source > > code when the build tries to link class from other modules. > > > > How does maven handle module dependencies? Does it build and publish the > > modules as listed in the modules section to the local repository? Then > when > > building subsequent modules does it link with those in the local > repository? > > > > Why might maven be finding old jars as dependencies? > > > > -Dave > > > -- 漠洋(苏琳冲) SuLinchong Phone 13656669328 Qq 387973308 Msn [email protected]
