Hello Marvin, I'm experiencing similar issue with Maven in large multi-module projects, especially if they are of >2 depth and one wants to apply same version to several modules of same maven project. Currently I have to go through all of the pom's and set version manually, with risk of making a mistake or incomplete change along the way.
"Maven - The Definitive Guide"<http://www.sonatype.com/book/pdf/maven-definitive-guide.pdf>states: *"When a project specifies a parent project, Maven uses that parent POM as a starting point before it reads the current project's POM. It inherits everything, including the groupId and version number."* It seems to me that this starting point processing is part of Maven's "validate" lifecycle phase, and that command line properties are not used in code which resolves parent coordinates (artifactId, groupId, and version). Maybe some of Maven developers or experts might confirm this and answer if this is a bug or a design goal. Regards, Stevo. On Wed, Sep 17, 2008 at 11:57 PM, Marvin Froeder <[EMAIL PROTECTED]> wrote: > Hi folks, > > I'm trying to do something like this: > > <?xml version="1.0" encoding="UTF-8"?> > <project> > <modelVersion>4.0.0</modelVersion> > > <parent> > <groupId>mygroup</groupId> > <artifactId>myparentartifact</artifactId> > <version>${version}</version> > </parent> > > <artifactId>myartifact</artifactId> > > </project> > > and launch maven like this: > mvn -Dversion=1.0 clean install > > To define parent version at runtime. > > But I always get: > > > > D:\flex\workspace\sonatype-flex-mojos\test-harness\src\test\resources\simple-flex-application>mvn > > -Dversion=2.0M6-SNAPSHOT clean install > > > [INFO] Scanning for projects... > > > Downloading: > > > http://192.168.1.3:8081/nexus/content/groups/all//info/flex-mojos/flex-super-pom/${version}/flex-super-pom-${version}.pom<http://192.168.1.3:8081/nexus/content/groups/all//info/flex-mojos/flex-super-pom/$%7Bversion%7D/flex-super-pom-$%7Bversion%7D.pom> > < > http://192.168.1.3:8081/nexus/content/groups/all//info/flex-mojos/flex-super-pom/$%7Bversion%7D/flex-super-pom-$%7Bversion%7D.pom > > > > > Downloading: > > > http://repo1.maven.org/maven2/info/flex-mojos/flex-super-pom/${version}/flex-super-pom-${version}.pom<http://repo1.maven.org/maven2/info/flex-mojos/flex-super-pom/$%7Bversion%7D/flex-super-pom-$%7Bversion%7D.pom> > < > http://repo1.maven.org/maven2/info/flex-mojos/flex-super-pom/$%7Bversion%7D/flex-super-pom-$%7Bversion%7D.pom > > > > > [INFO] > > ------------------------------------------------------------------------ > > > [ERROR] FATAL ERROR > > > [INFO] > > ------------------------------------------------------------------------ > > > [INFO] Failed to resolve artifact. > > > > > GroupId: info.flex-mojos > > > ArtifactId: flex-super-pom > > > Version: ${version} > > > > > Reason: Unable to download the artifact from any repository > > > > > info.flex-mojos:flex-super-pom:pom:${version} > > > > > from the specified remote repositories: > > > central (http://repo1.maven.org/maven2), > > > local (http://192.168.1.3:8081/nexus/content/groups/all/) > > > I'm doing that for integration tests. > > Is this a bug or am I doing something wrong? > > > VELO >
