[ http://issues.apache.org/jira/browse/COCOON-1890?page=comments#action_12428152 ] Ralph Goers commented on COCOON-1890: -------------------------------------
I guess in general I agree with you. However, if we go with the Maven fix when it is available it will have an impact on end users. We will need to make our master pom available to them to use to get all the versions Cocoon is using. But you are right that the current tool will be fairly invisible. > Provide a tool to update artifact versions within multiple POMs > --------------------------------------------------------------- > > Key: COCOON-1890 > URL: http://issues.apache.org/jira/browse/COCOON-1890 > Project: Cocoon > Issue Type: Task > Components: - Build System: Maven > Affects Versions: 2.2-dev (Current SVN) > Reporter: Andreas Hochsteger > Attachments: update-artifact-version.zip > > > When doing releases with Maven you have to modify many POMs to reflect the > correct artifact versions. > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
