You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Jackson (JIRA)" <ji...@codehaus.org> on 2007/07/19 06:22:13 UTC
[jira] Created: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Paul Sundling (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103473 ]
Paul Sundling commented on MCHANGELOG-66:
-----------------------------------------
The original comment set the property for the scm plugin. It seems I only need to set the system property for the changelog plugin with version 2.1, but will it hurt anything else not to have that configuration repeated for the scm plugin.
perhaps some of my confusion comes from <systemProperties> which presumably is shared over everything, but since it's set within the plugin config I wasn't sure if there was some namespace, like environment only seen for the plugin. I hadn't run into <systemProperties> before.
> 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Paul Sundling (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103474 ]
Paul Sundling commented on MCHANGELOG-66:
-----------------------------------------
Doh!
Just realized the changelog website hasn't been published since 11 Jul 2007 so the documentation is probably just not visible yet, as you mentioned adding documentation. Sorry for jumping the gun on this.
> 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Paul Sundling (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103472 ]
Paul Sundling commented on MCHANGELOG-66:
-----------------------------------------
Since I don't see any place besides this JIRA to find out about the extra config you have to do for Perforce (maven.scm.perforce.clientspec.name), could you add it to the FAQ?
Thanks for the fix, but it won't help others if they don't know where to look.
> 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
[jira] Issue Comment Edited: (MCHANGELOG-66) changelog for perforce
fails because of default clientspec
Posted by "Sebastian Annies (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102683 ]
Sebastian Annies edited comment on MCHANGELOG-66 at 7/19/07 7:10 AM:
---------------------------------------------------------------------
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 clients 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.
was:
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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Brian Jackson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102688 ]
Brian Jackson commented on MCHANGELOG-66:
-----------------------------------------
Dennis, that was super quick, thank you. I tested it and it works beautifully! When will 2.1 be released?
> 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
>
> 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Sebastian Annies (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102686 ]
Dennis Lundberg commented on MCHANGELOG-66:
-------------------------------------------
I've deployed a new 2.1-SNAPSHOT that allows you to configure system properties in the same way as maven-scm-plugin. Just as Brian demonstrated in his configuration earlier. Could you please give the new SNAPSHOT a try and see if it can solve this issue.
We also need to document this in the plugin site.
> 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
>
> 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103475 ]
Dennis Lundberg commented on MCHANGELOG-66:
-------------------------------------------
>From what I understand you need to have this config if you want perforce to work for the changelog plugin:
{code}
<plugin>
<artifactId>maven-changelog-plugin</artifactId>
<configuration>
<systemProperties>
<property>
<name>maven.scm.perforce.clientspec.name</name>
<value>${perforce.clientspec.name.from.settings.xml}</value>
</property>
</systemProperties>
</configuration>
</plugin>
{code}
If Brian would be so kind and confirm that, I can add it to the FAQ.
You need to set the system property in all plugins that need to use perforce through maven-scm. The plugin also needs to support it such a configuration of course. It doesn't use namespaces - it's the normal Java system properties. But, because plugins have their own little space that they run in, you need to set the system property for each plugin.
> 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
[jira] Closed: (MCHANGELOG-66) changelog for perforce fails because
of default clientspec
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGELOG-66.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.1
Added documentation as well.
> 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Brian Jackson (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102684 ]
Dennis Lundberg commented on MCHANGELOG-66:
-------------------------------------------
I agree that it seems that the support for Perforce in Maven SCM is not yet optimal.
By adding the support of system properties to maven-changelog-plugin, that works in the same way that it does for maven-scm-plugin, we at least have something that works until the Perforce provider in Maven SCM can be fixed.
> 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103476 ]
Dennis Lundberg commented on MCHANGELOG-66:
-------------------------------------------
*ducking the flames*
Seems I forgot to publish the site :-(
I just did a site:deploy. It should show up as soon as it is synced.
> 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
[jira] Commented: (MCHANGELOG-66) changelog for perforce fails
because of default clientspec
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102718 ]
Dennis Lundberg commented on MCHANGELOG-66:
-------------------------------------------
Thanks for testing this.
I'll write up some documentation on this and then I'll restart the release vote.
> 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
>
> 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