Hello, simply omit the <version> element in the child module and version will be inherited from the parent.
Regards, htfv (Aliaksei Lahachou) On Thu, Jul 5, 2012 at 10:53 AM, cortes <[email protected]> wrote: > > I have also this structure > > parent > module1 > child1_module1 > child2_module1 > module2 > > > I have seen on this > > http://docs.codehaus.org/display/MAVEN/best+practices+-+version+management+in+multi+project+bu > > that I can set in the parent something like this > > > <project> > <modelVersion>4.0.0</modelVersion> > <groupId>org.someproject</groupId> > <artifactId>project-root</artifactId> > <version>1</version> > <name>Some Project (Root)</name> > > <properties> > <applicationVersion>1.0-SNAPSHOT</applicationVersion> > </properties> > > ... > </project> > > and in the child > > > <project> > <modelVersion>4.0.0</modelVersion> > <parent> > <groupId>org.someproject</groupId> > <artifactId>project-root</artifactId> > <version>1</version> > </parent> > > <artifactId>project-core</artifactId> > <version>${applicationVersion}</version> > <name>Some Project Core</name> > > but if the child has another children I have to reset the properties if I > have understand well.. > > Why in this example is not specified where is the parent with the tag > relativePath? > > Thank you very much for the support > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Maven-Version-with-multimodule-project-tp5713074p5713077.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
