You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sebastian Annies (JIRA)" <ji...@codehaus.org> on 2007/07/19 14:12:13 UTC
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102683 ]
Sebastian Annies commented on MCHANGELOG-66:
--------------------------------------------
I don't think that this is a issue with the changelog plugin. There are many issues filed for the perforce scm provider that all deal with the same problem (and that is the problem here, too):
The Perforce SCM Provider does not know under which client the files are located.
This problem can only be fixed partly with the clientspec.name system property since there is only one system property in a system but we have several client as it is the case with continuum.
-> The Perforce SCM Provider should deal with this issue exactly as perforce users deal with it everyday: We use a .p4config with clientspec name in it.
> 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