jaxzin wrote:
Well, I think I fixed the problem but its not ideal.  I got the scm:changelog
goal to work if I add the following system property on the command line like
this:

mvn scm:changelog -Dmaven.scm.perforce.clientspec.name=MY_WORKSPACE_NAME

So I thought awesome, I'll just add the property to either my POM or my
settings.xml and the problem is solved.  Nope, if I move the property off
the command line and into the settings.xml or into the POM then I'm back to
square one and the client spec name is auto generated again.

Help!  Why isn't the provider only recognizing the property when its on the
command-line?



jaxzin wrote:
I'm trying to use the changelog with Perforce but after some
investigation it appear that the SCM provider for Perforce in not
creating the necessary client.  The changelog plugin executes this
command:

p4 -p perforce:1666 -c
JACKSBRR-LW-CT-JACKSBRR-MavenSCM-C:\Projects\SuperPOMs\espn filelog -t
-l ...

It must be failing silently because when I try to execute the same
command I get this error:

... - must create client
'JACKSBRR-LW-CT-JACKSBRR-MavenSCM-C:\Projects\SuperPOMs\espn' to access
local files.

My changelog config is:

            <plugin>

                <artifactId>maven-changelog-plugin</artifactId>

                <version>2.0-SNAPSHOT</version>

                <reportSets>

                    <reportSet>

                        <id>perforce-report</id>

                        <configuration>

                            <type>range</type>

                            <range>10</range>

                            <properties>

<maven.changelog.factory>org.apache.maven.perforcelib.PerforceChangeLogF
actory</maven.changelog.factory>

                            </properties>

                            <dateFormat>yyyy/MM/dd HH:mm:ss</dateFormat>

                            <basedir>${basedir}</basedir>

                        </configuration>

                        <reports>

                            <report>changelog</report>

                            <report>file-activity</report>

                            <report>dev-activity</report>

                        </reports>

                    </reportSet>

                </reportSets>

            </plugin>




It isn't a plugin property but a system property that is used by Maven-SCM.
Actually, the changelog plugin doesn't support the configuration of system properties in the plugin configuration.

Can you file an issue?
and if you have some time, this feature is already implemented in the Maven-SCM plugin goals, so you can take le code from them, patch the changelog plugin with it and attach the patch to the issue.

Emmanuel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to