[ http://jira.codehaus.org/browse/MPCHANGES-33?page=comments#action_85106 ] Dennis Lundberg commented on MPCHANGES-33: ------------------------------------------
I also think that we need to make this configurable in all plugins. It was pretty straight forward for the changes plugin. I'll look at creating patches for the other ones as well. A quick search in the plugins tree revealed the same plugins that Lukas mentioned. We should use the same property for all plugins. Is the name "maven.changes.file" that I used in my patch a good one? Should I create one issue for each of the affected plugins and link those issues to this one as being related? > Make it possible to configure the location of the changes.xml file > ------------------------------------------------------------------ > > Key: MPCHANGES-33 > URL: http://jira.codehaus.org/browse/MPCHANGES-33 > Project: maven-changes-plugin > Issue Type: New Feature > Affects Versions: 1.7 > Reporter: Dennis Lundberg > Fix For: 1.7.1 > > Attachments: MPCHANGES-33.patch > > > It is useful for people that are in a transition from Maven 1 to Maven 2 to > be able to move the changes.xml file to another location that the default > one. The attached patch introduces a new property "maven.changes.file" that > can be used to configure the location of the file. The default value is the > same as what has been used in the previous versions. -- 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
