changelog for perforce fails because of default clientspec
----------------------------------------------------------
Key: MCHANGELOG-66
URL: http://jira.codehaus.org/browse/MCHANGELOG-66
Project: Maven 2.x Changelog Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Brian Jackson
Currently changelog fails for Perforce when the default clientspec is used and
the plugin provides no way to supply the clientspec name. Currently you can do
the following for the scm plugin so that the scm:changelog will work:
<plugin>
<artifactId>maven-scm-plugin</artifactId>
<configuration>
<systemProperties>
<property>
<name>maven.scm.perforce.clientspec.name</name>
<value>${perforce.clientspec.name.from.settings.xml}</value>
</property>
</systemProperties>
</configuration>
</plugin>
I propose the same for the changelog report plugin.
--
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
