You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "sachin kamdar (JIRA)" <ji...@codehaus.org> on 2007/02/02 04:48:29 UTC
[jira] Closed: (MNG-2787) Multi Project Aggregator ignoring
dependency version in the POM
[ http://jira.codehaus.org/browse/MNG-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sachin kamdar closed MNG-2787.
------------------------------
Resolution: Fixed
the patch in MNG-1245 resolves the issue
> Multi Project Aggregator ignoring dependency version in the POM
> ---------------------------------------------------------------
>
> Key: MNG-2787
> URL: http://jira.codehaus.org/browse/MNG-2787
> Project: Maven 2
> Issue Type: Bug
> Components: POM, Reactor and workspace
> Affects Versions: 2.0.4
> Environment: XP Professional SP2
> Reporter: sachin kamdar
>
> I am using an aggregator pom to manage multi module project like below.
> poc-aggregator
> - pom.xml
> poc-ejb
> -pom.xml
> poc-web
> -pom.xml
> poc-core
> -pom.xml
> Both poc-ejb and poc-web has a dependency on poc-core, I build, package, install these projects using aggregator pom into my local repository. They work fine, the reactor builds them in the right order and so forth... until, I had to change poc-core to cater for a specific functionality of poc-web.
> So I made the change to the poc-core and incremented its version in the pom.xml to 1.1.0 from 1.0.0. I changed the dependency in poc-web to refer to the newer version 1.1.0. poc-ejb is still referring to 1.0.0 as it does not need/care about this change.
> so now I have poc-core 1.0.0 installed in my local repository which is referenced by poc-ejb. I have the source updated for poc-core to 1.1.0 which is referenced by the poc-web.
> when I do the package or install via aggregator (which has poc-ejb, poc-web and poc-core as modules), Maven changes the poc-core reference in the poc-ejb project to 1.1.0. It seems to be overwriting the explicit reference to version 1.0.0 with the source version 1.1.0.
> This is potentially dangerous and buggy. When I have an explicit reference to the dependency which exists in the repository I expect it to be picked up or thrown an error if it does not exist.
> Please tell me if you need more info.
--
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