Hi! On 21 Jul 2008, Taras Lipatov wrote:
> Does any one know, > > when releasing a multi-module project from the project parent.. > > I have two modules: "core" and "webapp" > > "core" module is version 1.0.0-SNAPSHOT > "webapp" has a dependency on "core:1.0.0-SNAPSHOT" > > When running release:prepare... > "webapp" pom is transformed and dependency "core:1.0.0-SNAPSHOT" is now > "core:1.0.0" which is correct sense that's the version of core that's > being released. > > How ever the "webapp" module complains that it cannot find "core:1.0.0" > Even though "core" is declared 1st in the parent pom. The problem is very likely not to be with the release plugin but with your packaging. Try a "mvn -o package" from your parent directory with an empty repository (empty means none of YOUR modules in the local repo). I bet it's going to fail. What packaging is set in your parent, the core and the webapp? Maven should be able to find all three modules when building from the parent. If not something's wrong. I had (partly still have) similar problems with EARs and skinny WARs. > Is there any way to do this in one shot? Yes, fix the packaging problem and the release will work. hth, - martin
signature.asc
Description: PGP signature
