You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Jackson, Brian R" <Br...@espn3.com> on 2007/07/17 07:56:16 UTC
changelog and perforce
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>
Re: changelog and perforce
Posted by Emmanuel Venisse <em...@venisse.net>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: changelog and perforce
Posted by "Sundling, Paul" <pa...@sonyconnect.com>.
As a matter of fact I am delighted to hear it's fixed. So it was a bug
after all. :)
I thought maybe I was missing some piece of configuration. In a way I
was, given your workaround using the clientspec name. :)
Paul Sundling
-----Original Message-----
From: Dennis Lundberg [mailto:dennisl@apache.org]
Sent: Thursday, July 19, 2007 4:02 AM
To: Maven Users List; Sundling, Paul
Subject: Re: changelog and perforce
Thanks for looking into this Brian.
I started a vote to release the changelog-plugin the other day. I'll
stop that vote and try to squeeze in a fix for this problem as well. I'm
sure that Paul Sundling will be delighted to read why this isn't
working.
I'll see what I can do about it and will make any further comments in
JIRA:
http://jira.codehaus.org/browse/MCHANGELOG-66
jaxzin wrote:
> So I found my problem was actually two problems.
>
> 1) When I moved the property into the settings.xml, the profile I
> added it to was defined without any activation criteria which for many
> purposes makes it act as if the profile is always active but withe
> inconsistant exception for the properties defined in that profile.
> The solution: I added the profile to the activeProfiles clause in the
settings.xml.
>
> 2) The scm goals have a configuration property named
> 'systemProperties' that I needed to use.
>
> So that got the scm:changelog working without having the clientspec
> property specified on the command-line. Unfortuately this doesn't fix
> my problem for the changelog:changelog report goal. I can run it on
> command-line with the property but it doesn't have the equivalent of
> the 'systemProperties' configuration. So for running 'mvn site' even
> the command-line doesn't work because the changelog report plugin
> forks the lifecycle. So I'm pretty sure I'm stuck without a bug fix
> to changelog. I filed a JIRA issue for it:
> http://jira.codehaus.org/browse/MCHANGELOG-66.
>
>
>
> 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.PerforceChange
>>> LogF
>>> 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>
>>>
>>>
>>>
>>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: changelog and perforce
Posted by Dennis Lundberg <de...@apache.org>.
Thanks for looking into this Brian.
I started a vote to release the changelog-plugin the other day. I'll
stop that vote and try to squeeze in a fix for this problem as well. I'm
sure that Paul Sundling will be delighted to read why this isn't working.
I'll see what I can do about it and will make any further comments in JIRA:
http://jira.codehaus.org/browse/MCHANGELOG-66
jaxzin wrote:
> So I found my problem was actually two problems.
>
> 1) When I moved the property into the settings.xml, the profile I added it
> to was defined without any activation criteria which for many purposes makes
> it act as if the profile is always active but withe inconsistant exception
> for the properties defined in that profile. The solution: I added the
> profile to the activeProfiles clause in the settings.xml.
>
> 2) The scm goals have a configuration property named 'systemProperties' that
> I needed to use.
>
> So that got the scm:changelog working without having the clientspec property
> specified on the command-line. Unfortuately this doesn't fix my problem for
> the changelog:changelog report goal. I can run it on command-line with the
> property but it doesn't have the equivalent of the 'systemProperties'
> configuration. So for running 'mvn site' even the command-line doesn't work
> because the changelog report plugin forks the lifecycle. So I'm pretty sure
> I'm stuck without a bug fix to changelog. I filed a JIRA issue for it:
> http://jira.codehaus.org/browse/MCHANGELOG-66.
>
>
>
> 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>
>>>
>>>
>>>
>>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: changelog and perforce
Posted by jaxzin <Br...@espn3.com>.
So I found my problem was actually two problems.
1) When I moved the property into the settings.xml, the profile I added it
to was defined without any activation criteria which for many purposes makes
it act as if the profile is always active but withe inconsistant exception
for the properties defined in that profile. The solution: I added the
profile to the activeProfiles clause in the settings.xml.
2) The scm goals have a configuration property named 'systemProperties' that
I needed to use.
So that got the scm:changelog working without having the clientspec property
specified on the command-line. Unfortuately this doesn't fix my problem for
the changelog:changelog report goal. I can run it on command-line with the
property but it doesn't have the equivalent of the 'systemProperties'
configuration. So for running 'mvn site' even the command-line doesn't work
because the changelog report plugin forks the lifecycle. So I'm pretty sure
I'm stuck without a bug fix to changelog. I filed a JIRA issue for it:
http://jira.codehaus.org/browse/MCHANGELOG-66.
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>
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/changelog-and-perforce-tf4095216s177.html#a11682575
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: changelog and perforce
Posted by jaxzin <Br...@espn3.com>.
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>
>
>
>
--
View this message in context: http://www.nabble.com/changelog-and-perforce-tf4095216s177.html#a11681777
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org