[ 
https://jira.codehaus.org/browse/MVERSIONS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296517#comment-296517
 ] 

Gagandeep commented on MVERSIONS-123:
-------------------------------------

Given that this plugin doesn't support what Cornel Masson wants, can you 
suggest some code to find the dependency in a submodule when the corresponding 
version property is defined in the parent pom? The "wnr" and "as" object under 
returns nothing when the property is defined in the parent pom. Any way around 
to actually update the property even if it's defined in parent?

ArtifactVersion wnr = version.getNewestVersion( currentVersion, property, 
this.allowSnapshots, this.reactorProjects, this.getHelper() ); 
ArtifactAssociation[] as = version.getAssociations();
                
> Version properties inparent not picked up by e.g. display-property-updates
> --------------------------------------------------------------------------
>
>                 Key: MVERSIONS-123
>                 URL: https://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, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.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