[
http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103553
]
Brian Jackson commented on MCHANGELOG-66:
-----------------------------------------
Dennis, yup that is exactly what works. I highly recommend everyone NOT use
the same setting for the scm plugin as it will hose your client spec when doing
a release. It's a reported bug in the release plugin but I don't remember the
JIRA key off the top of my head.
> 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
> Assignee: Dennis Lundberg
> Fix For: 2.1
>
>
> 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
