[ http://jira.codehaus.org/browse/SCM-119?page=comments#action_53562 ]
mike perham commented on SCM-119: --------------------------------- I believe those old plugins are fundamentally broken. For instance the changelog plugin does NOT use the Maven SCM subsystem but rather its own SCM adapters (see the plugin code, it's true!). Other plugins like the release plugin DO use Maven SCM. The issue is that they both use the same SCM URL. Now Maven SCM assumes the URL ends in a directory name or a "/". Those other plugins assume the URL ends in "/...". There is no way to resolve this - one or the other must be changed and I believe it is the reporting plugins which must change to use the SCM subsystem. I will open a new issue for them. > Perforce provider should only append "/..." to view if necessary > ---------------------------------------------------------------- > > Key: SCM-119 > URL: http://jira.codehaus.org/browse/SCM-119 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Reporter: Neil Padgen > Attachments: patch > > > When creating a clientspec, maven-scm-provider-perforce currently appends > "/..." to the SCM URL regardless of what is already there. But other plugins > (such as the changelog-report-plugin, file-activity-report-plugin and > developer-activity-report-plugin) require the SCM URL to end in "/..." to be > able to produce output. > Fix: when creating the clientspec, only append "/..." if it is not already > there. > (I'm not sure if "p4 filelog" is invoked by this component or those other > report plugins.) > *Untested* patch attached. -- 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
