I didn't find a bug in Jira. Think you should add one : http://jira.codehaus.org/browse/MRELEASE
On Mon, Jul 14, 2008 at 3:01 PM, Richard Chamberlain < [EMAIL PROTECTED]> wrote: > I have the problem when I also use the following: > > parent-pom.xml: > <modules> > <module>..\test-module</module> > </modules> > > So this is a known bug? Or should I raise an issue about this? It seems as > though the release plugin should be able to cope if a "mvn install" works > ok. > > Regards, > > Richard > > -----Original Message----- > From: Julien Lamandé [mailto:[EMAIL PROTECTED] > Sent: 14 July 2008 13:49 > To: Maven Users List > Subject: Re: release plugin issues with a multi-module project > > The release plugin works well with multi-modules projects. > But it breaks with this kind of layout. > > To make your layout works, you surely had to add in modules poms a > relativePath tag to ../Parent, e.g : > <parent> > <groupId>yourGroupId</groupId> > <artifactId>Parent</artifactId> > <version>1.0-SNAPSHOT</version> > *<relativePath>../Parent</relativePath>* > </parent> > > This is where the release plugin fails out. > > > On Mon, Jul 14, 2008 at 10:18 AM, Richard Chamberlain < > [EMAIL PROTECTED]> wrote: > > > Hi All, > > > > > > > > I've had some issues releasing our project, I hope you can help. > > > > > > > > The folder structure used to be like: > > > > > > > > Parent > > > > + > > > > - Module1 > > > > - Module2 > > > > > > > > The three projects were mounted in eclipse and everything went fine, > > releasing was a breeze etc. > > > > > > > > However the perforce plugin got really confused with the same files > > appearing in 2 projects. So, we moved to: > > > > > > > > - Parent > > > > - Module1 > > > > - Module2 > > > > > > > > This solved our eclipse perforce plugin issue and building was great. > Until > > we came to do a release. > > > > > > > > It seems as though it takes the parent module and checks everything in > the > > parent folder to: > > > > - Parent/target/checkout > > > > > > > > And then builds from there. This used to work as modules were nested in > the > > parent. This is no longer the case and the build breaks. > > > > > > > > This seems to be an issue with the release plugin not supporting the > > <modules> tag in pom.xml of the parent. > > > > > > > > Has anyone else experienced this? Is there a workaround? We're stuck > > between an issue with the perforce eclipse plugin and the > > maven-release-plugin > > > > > > > > I've attached a simple test project that illustrates the issue. > > > > > > > > Thanks, > > > > > > > > Richard > > > > > > > > > > > > *Richard Chamberlain * > > Software Engineer | Caplin Systems Ltd > > > > Office: +44 (0)20 7826 9639 > > Mobile: +44 (0)7720 686 064 > > www.caplin.com > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
