Re: ${project-version} breaks maven 3 build

[Cihan Cimen <ci...@srdc.com.tr>]

Hi,

I have a problem that may be related to this issue.
When I have a dependency to 
org.apache.stanbol:org.apache.stanbol.enhancer.servicesapi:bundle:0.9-SNAPSHOT 
,
enhancer.parent can not be found by maven because it always searches for 
version ${stanbol-version}.
I use maven 2.2.1. I have Apache Stanbol on my local maven repo, built 
successfully.

Enclosed, please find an example pom.xml with a simple dependency on 
enhancer.servicesapi and the output of "mvn clean install 
-Dstanbol-version=0.9-SNAPSHOT" command.

Best,
-Cihan

On 03/31/2011 03:24 PM, Bertrand Delacretaz wrote:
> 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)
>
>