Jakob, that's very tricky but it doesn't make it much easier.
Using this method every child module must set its own version number (pom.xml: project/version) instead of project/parent/version. It's about as broad as it's long. ;-) -chris Am Dienstag, 7. März 2006 15:55 schrieb Jakob Vad Nielsen: > Hi Christian, > > I do not know if there is a way to skip the version, but there is a > solution to your problem. > > Set the parent version to for example 1.0-SNAPSHOT. Then the sub modules > will always update the main project settings. > > /Jakob > > -----Opprinnelig melding----- > Fra: Christian Mouttet [mailto:[EMAIL PROTECTED] > Sendt: 7. mars 2006 09:28 > Til: [email protected] > Emne: multi module projects > > Hi, > > imagine following project structure: > > main-project > ! pom.xml (version x.y) > ! > +- module-a > ! pom.xml (parent = main-project-x.y > ! default relativePath = ../pom.xml) > ! > +- module-b > pom.xml (parent is main-project-x.y > default relativePath = ../pom.xml) > > I know that relative path is first used to find the parent pom.xml. If > it's > not found then it is searched in the repositories (local, central). > > Is there a way to avoid the version number if I surely know that the > parent > pom.xml lives in the relative path? I don't want manually change the > version > in all submodules if the parent version changes. > > > Regards > > -chris ********************************************************************** Diese E-Mail wurde auf Viren ueberprueft. [EMAIL PROTECTED] ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
