cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <>
Subject [jira] Commented: (COCOON-1890) Provide a tool to update artifact versions within multiple POMs
Date Sun, 13 Aug 2006 19:53:14 GMT
    [ ] 
Ralph Goers commented on COCOON-1890:


What do you thing MNG-1577 is about?

In Maven 1 you could create a file and put the version of every jar you wanted
to use. You could share that property file across multiple projects so they would all be in
synch.  Maven 2 provides a similar concept in that it allows you to specify the version of
a dependency in the root pom's dependencyManagement section.  The problem with the implementation
in Maven 2 is that, unlike Maven 1, it is not an override - so if a transitive dependency
(or any dependency for that matter) specifies a version the version specified in the dependencyManagement
section is not used.

Fixing MNG-1577 would mean that to keep all 20 poms in synch would mean updating the dependencyManagement
section in the root pom. versions in child poms would be meaningless.

That is why I am -1 on the fix proposed here as it is simply a hack to get around a real problem
in Maven. Please go to MNG-1577 and add your vote to that issue instead of looking for workarounds

Unless you can convince me that this problem has problem has nothing to do with keeping dependency
versions in synch across blocks, I will continue to express my -1 on this fix.

> Provide a tool to update artifact versions within multiple POMs
> ---------------------------------------------------------------
>                 Key: COCOON-1890
>                 URL:
>             Project: Cocoon
>          Issue Type: Task
>          Components: - Build System: Maven
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Andreas Hochsteger
>         Attachments:
> When doing releases with Maven you have to modify many POMs to reflect the correct artifact
> The problem is, that the whole repository should always use the consistent artifact versions.
> Reinhard talked to me about this problem and I tried to put togeather a quick script
combined with an XSL which could do this task.
> Attached is a first version (docs and comments within the files) which does the job.
> It would be great, if somebody could give it a try and provide some feedback.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message