[ http://jira.codehaus.org/browse/MPCHANGES-33?page=comments#action_85111 ]
Arnaud Heritier commented on MPCHANGES-33:
------------------------------------------
Yes, the name of the property you proposed is fine for me.
You can use this issue in others plugins (for the issue # in the changes file).
You can also add on these plugins a constraint like :
{code:xml}
<!-- fake test because the assert:assertPluginAvailable tag is avalaible in the
maven-plugin-plugin 1.7 and newer. Thus maven will break if it's not present.
-->
<assert:assertPluginAvailable groupId="maven" artifactId="maven-plugin-plugin"
minRelease="1.7" neededBy="${plugin.artifactId}"/>
<assert:assertPluginAvailable groupId="maven" artifactId="maven-changes-plugin"
minRelease="1.7.1" neededBy="${plugin.artifactId}"/>
{code}
> 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
