[ http://issues.apache.org/jira/browse/COCOON-1890?page=comments#action_12428143 ] Ralph Goers commented on COCOON-1890: -------------------------------------
Well, I do have the right. However, in this case I'll change my veto to a -0 (with caveats). I certainly understand the predicament Cocoon is in - it is holding up my organization from switching from Maven 1 to Maven 2 altogether. My caveat is that I'd simply like agreement that when this fix is done that Cocoon take advantage of it (frankly, I think that is a no-brainer so I'm not really worried). As far as the root problem goes, since my manager will let me work on the Maven issue on company time I should be able to work on it within the next couple of weeks. > 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
