Hi,

mvn help:effective-pom (for example) fails with Maven 3 because of
this in most stanbol POMs:

 <parent>
    <groupId>org.apache.stanbol</groupId>
    <artifactId>stanbol-parent</artifactId>
    <version>${stanbol-version}</version>
    <relativePath>parent</relativePath>
  </parent>

And stanbol-version is defined in the parent pom, creating a
chicken-and-egg problem.

For some reason Maven 2 accepts that, but I think it's wrong anyway,
version numbers should be constants in general, and especially when
pointing to the parent pom. I think variable version numbers will
cause problems with the Maven release plugin, at least.

Can we change to constants for version numbers, or what was the idea
behind this?

-Bertrand

(workaround is to add -Dstanbol-version=0.9-SNAPSHOT to the mvn
command line in the meantime)

Reply via email to