[ 
http://jira.codehaus.org/browse/MVERSIONS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cornel Masson updated MVERSIONS-123:
------------------------------------

    Attachment: versiontest.zip

The attached example demonstrates the problem. Run:

{noformat}
$ cd versiontest
$ mvn versions:display-property-updates
{noformat}

and you'll get: "This project does not have any properties associated with 
versions"

But then move the <junit.version> property from the parent down to {{moduleA}}, 
and it works:

{noformat}
The following version property updates are available:
${junit.version} ......................... 3.8.1 -> 4.8.1
{noformat}

> Version properties inparent not picked up by e.g. display-property-updates
> --------------------------------------------------------------------------
>
>                 Key: MVERSIONS-123
>                 URL: http://jira.codehaus.org/browse/MVERSIONS-123
>             Project: Maven 2.x Versions Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Windows XP
> Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
> Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing)
>            Reporter: Cornel Masson
>         Attachments: versiontest.zip
>
>
> The goals operating on *property* controlled version numbers (e.g. 
> display-property-updates) only work if the properties are defined in the 
> targeted POM itself, not in a parent POM.
> Example:
> If module *B* has a dependency on module A, declared in B as follows:
> <dependency>
>       <groupId>com.my.test</groupId>
>       <artifactId>module-A</artifactId>
>       <version>${module-A.version}</version>
> </dependency>
> but ${module-A.version} is not defined in B's own POM, but its *parent*, then 
> the plugin doesn't pick it up - it simply says:
> "This project does not have any properties associated with versions"
> This is a major problem for us, since all our dependency version properties 
> are defined in each project's root POM, i.e. the parent of all sub-modules in 
> that project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to