I hade the same issue. I solved it by using the preparationGolas maven-release-plugin in order to do an install instead of integration-test:
<configuration> <preparationGoals>clean install</preparationGoals> </configuration> cheers, -tony Gilles Scokart wrote: > > Actually, to find a workaround, you don't need to deploy on a company > repository. You limit it to an local install. What I could suggest you > is to bind the install plugin to the latest phase (integration-test I > think) of the build launched by the release plugin. But I'm not sure it > would work. Indeed, maven has to find the dependencies before it launch > the build (to know in wich order to build). I have already build some > times ago a project with a similar structure, and what I did was to > release on module at a time (but there is maybe an better solution with > more recent versions). > > Note that when there is no dependencies between submodules, the release > plugin works correctly with multi-module project. > > By the way, did you tried similar things with only 1 level? In that case, > the maven is maybe able to find sibbling module. > > Gilles Scokart > -- View this message in context: http://www.nabble.com/Maven-Release-Plugin-Version-Problem-tf1902125s177.html#a7758815 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]