SCM-79

2005-11-22 Thread Mike Perham
I'm in the process of completing the rest of the operations on the Perforce provider. I've structured the code packaging similarly to the changelog command but my code format is not the maven standard (my company uses the Sun standard). Do you guys care, can you reformat the code for me when I su

RE: provider operations

2005-11-23 Thread Mike Perham
know if a file is modified locally and not committed. Do you have an equivalent in Perforce? Update command update all files in working copy with latest version of files that exists in scm repository. This command use internally in maven-scm the changelog command. Emmanuel Mike Perham a écrit

'No such provider: perforce'

2005-11-23 Thread Mike Perham
How do I get the DefaultScmManager to see my new Perforce provider? mike

RE: provider operations

2005-11-23 Thread Mike Perham
operation). The fstat command has a lot of flexibility to get that info from the server. -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 9:23 AM To: scm-dev@maven.apache.org Subject: RE: provider operations Status - Perforce does not keep any

RE: 'No such provider: perforce'

2005-11-23 Thread Mike Perham
lto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 7:48 PMTo: scm-dev@maven.apache.orgSubject: Re: 'No such provider: perforce' Take a look at other provider's components.xml.  Do you have one yet?   -Dan   On 11/23/05, Mike Perham <[EMAIL PROTECTED]> wrote: How do

RE: 'No such provider: perforce'

2005-11-24 Thread Mike Perham
earcase.regards,Wim 2005/11/24, Mike Perham <[EMAIL PROTECTED]>: [INFO] [INFO] Reactor Summary:[INFO] --

problems with cvs provider

2005-11-24 Thread Mike Perham
Two tests fail. junit.framework.AssertionFailedError: expected:<38403> but was:<39511> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert

RE: Clearcase unedit command

2005-11-24 Thread Mike Perham
I'm trying to use release:prepare and it's obvious that the release plugin does not work with locking SCM providers yet. You need to call the SCM 'edit' command to open the POM for write access in Perforce and (I assume) Clearcase. Shall I open a JIRA issue? Caused by: org.apache.maven.plugin.Mo

RE: Clearcase unedit command

2005-11-24 Thread Mike Perham
t: Re: Clearcase unedit command mvn -DuseEditMode=true release:prepare I added it for clearcase Emmanuel Mike Perham a écrit : > I'm trying to use release:prepare and it's obvious that the release > plugin does not work with locking SCM providers yet. You need to call > the SCM &#

RE: Clearcase unedit command

2005-11-24 Thread Mike Perham
Or am I missing something? mike -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 3:04 PM To: scm-dev@maven.apache.org Subject: Re: Clearcase unedit command mvn -DuseEditMode=true release:prepare I added it for clearcase Emmanuel

RE: [jira] Commented: (SCM-79) Add remaining operations to Perforce provider

2005-11-28 Thread Mike Perham
rations to Perforce provider > - > > Key: SCM-79 > URL: http://jira.codehaus.org/browse/SCM-79 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-perforce > Versions: 1.0-beta-2 > Reporter: mike perham >

RE: [jira] Commented: (SCM-79) Add remaining operations to Perforce provider

2005-11-28 Thread Mike Perham
> - can you add checkouted files in a list in checkout consuler like we > do it in svn provider? I added this and attached an 'svn diff' patch to the issue. I also attached a patch to fix several lingering issues with the commands - 'release:prepare' should work fully now. > - can we checkout

RE: [jira] Commented: (SCM-79) Add remaining operations to Perforce provider

2005-11-28 Thread Mike Perham
es the named workspace spec for the sync. -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Monday, November 28, 2005 4:34 PM To: scm-dev@maven.apache.org Subject: RE: [jira] Commented: (SCM-79) Add remaining operations to Perforce provider > - can you add checkouted f

Exercising more commands?

2005-11-29 Thread Mike Perham
How do I exercise the commands which are not used by the release plugin? I'm thinking mostly of the diff and changelog commands - are there any m2 plugins that use these commands? mike

RE: [jira] Created: (SCM-89) Add checkout to working directory support to Perforce

2005-11-29 Thread Mike Perham
Sans digging through all the code, what did you end up implementing?? Quoting "mike perham (JIRA)" <[EMAIL PROTECTED]>: > Add checkout to working directory support to Perforce > - > > Key: SCM-89 >

RE: Exercising more commands?

2005-11-29 Thread Mike Perham
Any samples or docs on how to use the plugin? -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 29, 2005 11:35 AM To: scm-dev@maven.apache.org Subject: Re: Exercising more commands? maven-scm-plugin in maven-scm tree Emmanuel Mike Perham a

RE: [jira] Commented: (SCM-89) Add checkout to working directory support to Perforce

2005-11-30 Thread Mike Perham
While we are being honest, I made Perforce login a no-op.  The user has to login manually before they can perform any operations.  This isn't a problem because Perforce logins are good for 12 hours so usually developers login once in the morning and work the rest of the day on that login.  

RE: Exercising more commands?

2005-11-30 Thread Mike Perham
o, Perforce won't be support in continuum 1.0.2 >> >>Mike Perham a écrit : >> >>>I don't have time to do this right now. It'll have to wait until we >>>deploy continuum here internally. >>> >>>-Original Message- >>&g

RE: [vote] Release SCM 1.0-beta-2

2005-12-05 Thread Mike Perham
I have not tested Peforce with Continuum but here's my +0.5 (pending approval as a committer :-) just to get it out there and have more people testing it in real life. Any chance of getting a new maven-release-plugin to go along with it or is that biting off too much? mike -Original Message-

Perforce changelog command?

2005-12-05 Thread Mike Perham
Who wrote this command? It doesn't work and I didn't notice until today when I tried to use the changelog report plugin. I will try to get a fix in by the end of day in hopes of making the upcoming release. mike

RE: Where are scm releases deployed?

2006-01-08 Thread Mike Perham
http://www.ibiblio.org/maven2/org/apache/maven/scm/ I guess the beta releases have not been sync'd to m1. -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Sunday, January 08, 2006 8:53 AM To: scm-dev@maven.apache.org Subject: Where are scm releases deployed? Hi

FW: [jira] Resolved: (SCM-113) Support persistent and transient clientspecs

2006-01-16 Thread Mike Perham
FYI this could also be useful to Clearcase from what I understand. -Original Message- From: Mike Perham (JIRA) [mailto:[EMAIL PROTECTED] Sent: Monday, January 16, 2006 2:31 PM To: scm-dev@maven.apache.org Subject: [jira] Resolved: (SCM-113) Support persistent and transient clientspecs

RE: [vote] Release Maven-SCM 1.0 final

2006-02-24 Thread Mike Perham
-0 I got several Perforce patches in the last 2-3 days that I would like to get in before the release. Do you mind if I sneak them in tomorrow? You are welcome to apply them if you have the time today (SCM-16x) but I'm slammed at work right now. -Original Message- From: Emmanuel Venisse

RE: [vote] Release Maven-SCM 1.0 final

2006-02-27 Thread Mike Perham
I'll wrap up the remaining update/changelog issue tonight. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 7:00 AM To: scm-dev@maven.apache.org Subject: Re: [vote] Release Maven-SCM 1.0 final The code is stable (need to apply patch of T

RE: SCM sources not available ?

2006-05-25 Thread Mike Perham
Title: Message This works for me: http://svn.apache.org/repos/asf/maven/scm/trunk/   Your command only has a single slash after the http: protocol.   From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2006 6:27 AMTo: scm-dev@maven.apache.orgSubject: SCM sources not av

Re: Synergy provider

2006-09-01 Thread Mike Perham
I'm not a lawyer but this is my understanding of how it works. When you donate a large amount of code like this to Apache, you are giving it to us to license under the APL as part of Maven itself. You cannot change the license nor can you put additional stipulations on distribution or usage of t

Re: Other scms...

2007-04-03 Thread Mike Perham
tted many months ago and seems to have been ignored :-) Ryan On 4/3/07, Mike Perham <[EMAIL PROTECTED]> wrote: > I'm not aware of any. If it's not here, it doesn't exist. > > http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/ > > > On 4

Re: [vote] Release Maven-SCM 1.0 final

2007-05-22 Thread Mike Perham
+1 On 5/22/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Hi, I'd like to release Maven-SCM-1.0 that contains few bug fixes found in rc1. The road map: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&styleName=Html&version=13380 Staging repo: http://people.apache.org/~eveni

Re: JRE version for providers

2007-07-30 Thread Mike Perham
>From http://maven.apache.org/download.html: JDK 1.4 or above (this is to execute Maven - it still allows you to build against 1.3 and prior JDK's) On 7/30/07, Gilles Scokart <[EMAIL PROTECTED]> wrote: > What is the JRE that the providers should assume?

Re: release:perform changes perforce clientspec

2007-12-12 Thread Mike Perham
Ken, I wrote the Perforce plugin for Maven but I don't use either technology at my current job (I'm now a Ruby guy) so I'm limited in how I can help you. I'm happy to answer what questions I can. To perform the release, Maven needs to build the canonical source as checked into Perforce. The only

Re: release:perform changes perforce clientspec

2007-12-12 Thread Mike Perham
You are not giving it a clientspec, you are giving it a name to use. It is assumed that Maven SCM can do whatever it wants with that clientspec (create it, modify it, delete it). It was done this way because there are corporations who have Peforce clientspec naming standards and absolutely will n

Re: release:perform changes perforce clientspec

2007-12-12 Thread Mike Perham
I guess I don't recall what your actual problem is. Can you summarize? On 12/12/07, brewk9 <[EMAIL PROTECTED]> wrote: > > > Thanks for your reply. Well, I'm supplying the clientspec to enable the > maven-changelog-plugin to work. Without that, that plugin doesn't work. > Should the perforce plugi

[jira] Created: (SCM-79) Add remaining operations to Perforce provider

2005-11-22 Thread mike perham (JIRA)
Reporter: mike perham Fix For: 1.0-beta-2 I am in the process of implementing the rest of the Perforce operations. I completed add, remove and checkin last night and should have the rest of the operations done in the next day. -- This message is automatically generated by JIRA. - If you

[jira] Created: (SCM-88) Add transparent support for locking providers

2005-11-29 Thread mike perham (JIRA)
Add transparent support for locking providers - Key: SCM-88 URL: http://jira.codehaus.org/browse/SCM-88 Project: Maven SCM Type: Improvement Components: maven-scm-api Versions: 1.0-beta-2 Reporter: mike

[jira] Created: (SCM-89) Add checkout to working directory support to Perforce

2005-11-29 Thread mike perham (JIRA)
Reporter: mike perham Fix For: 1.0-beta-2 Attached is a patch will adds the ability to check out code to an arbitrary directory as requested by Emmanuel and discussed by myself and Jeff Jensen last night on the scm-dev mailing list. -- This message is automatically generated by JIRA

[jira] Commented: (SCM-89) Add checkout to working directory support to Perforce

2005-11-29 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-89?page=comments#action_52321 ] mike perham commented on SCM-89: Emmanuel, please update the Peforce entry on the SCM Matrix to reflect that all operations are now supported. http://docs.codehaus.org/display/SCM/SCM

[jira] Updated: (SCM-89) Add checkout to working directory support to Perforce

2005-11-29 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-89?page=all ] mike perham updated SCM-89: --- Attachment: release_perform.txt release:prepare and release:perform now work on my machine. Huzzah! > Add checkout to working directory support to Perfo

[jira] Created: (SCM-92) Add working directory support to Perforce update command

2005-12-01 Thread mike perham (JIRA)
-2 Reporter: mike perham Fix For: 1.0-beta-2 Attachments: update.txt Attached is a patch which updates Perforce to use the exact same logic for both checkout and update. The update command is unused at this point and can be removed if you'd like. -- This message is automati

[jira] Updated: (SCM-92) Add working directory support to Perforce update command

2005-12-01 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-92?page=all ] mike perham updated SCM-92: --- Attachment: update2.txt Revised patch to wrap checkout command in the update command itself rather than in the provider. > Add working directory support to Perforce upd

[jira] Created: (SCM-97) Implement executable changelog command

2005-12-06 Thread mike perham (JIRA)
Implement executable changelog command -- Key: SCM-97 URL: http://jira.codehaus.org/browse/SCM-97 Project: Maven SCM Type: Bug Components: maven-scm-provider-perforce Versions: 1.0-beta-2 Reporter: mike perham

[jira] Commented: (SCM-110) Perforce should force sync

2005-12-12 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53295 ] mike perham commented on SCM-110: - If you do a release:perform, maven checks out the tagged source code to target/checkout and builds that to generate the official released binaries. If

[jira] Commented: (SCM-110) Perforce should force sync

2005-12-12 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53301 ] mike perham commented on SCM-110: - Well, the release process is relatively rare. How often do you release a new version of a project? Once a week when under heavy development, maybe

[jira] Commented: (SCM-110) Perforce should force sync

2005-12-12 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53302 ] mike perham commented on SCM-110: - Jeff, better? // Use a simple heuristic to determine if we should use the Force flag // on sync. Forcing sync is a HUGE performance

[jira] Updated: (SCM-110) Perforce should force sync

2005-12-12 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-110?page=all ] mike perham updated SCM-110: Attachment: force2.txt > Perforce should force sync > -- > > Key: SCM-110 > URL: http://jira.codehaus.org

[jira] Commented: (SCM-111) perforce: checkout doesn't work at all

2005-12-12 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-111?page=comments#action_53323 ] mike perham commented on SCM-111: - Robert, which version of p4 are you using? The code works fine for me and others and I'm on 2005.1. > perforce: checkout doesn'

[jira] Commented: (SCM-113) Support persistent and transient clientspecs

2005-12-14 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53419 ] mike perham commented on SCM-113: - Good idea on the Description. Note that Maven SCM does not know anything about the context in which it is running. It does not know that it is

[jira] Commented: (SCM-113) Support persistent and transient clientspecs

2005-12-14 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53428 ] mike perham commented on SCM-113: - No because the common case is that the SCM URL is in the POM and therefore can't be user or location-dependent. I can detect your username throug

[jira] Commented: (SCM-114) Clientspec naming

2005-12-15 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53488 ] mike perham commented on SCM-114: - The Perforce plugin will NOT obey P4CLIENT because it needs to support multiple clientspecs with Continuum. It will NOT obey P4PASSWD because it does

[jira] Commented: (SCM-119) Perforce provider should only append "/..." to view if necessary

2005-12-16 Thread mike perham (JIRA)
[ 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

[jira] Created: (SCM-121) Intermittent CVS test failures

2005-12-17 Thread mike perham (JIRA)
Intermittent CVS test failures -- Key: SCM-121 URL: http://jira.codehaus.org/browse/SCM-121 Project: Maven SCM Type: Bug Components: maven-scm-provider-cvs Versions: 1.0-beta-3 Reporter: mike perham Fix For: 1.0-beta

[jira] Created: (SCM-122) Starteam test failures when running a full SCM build

2005-12-17 Thread mike perham (JIRA)
Reporter: mike perham Fix For: 1.0-beta-3 Starteam tests fail when running as part of a bigger reactor build. All tests pass when building the module on its own. If you are doing File IO, make sure you take ${basedir} into account. -- This message is automatically generated by JIRA

[jira] Commented: (SCM-120) ClearCase Changelog test failure

2006-01-03 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-120?page=comments#action_54811 ] mike perham commented on SCM-120: - I believe this issue is due to timezones. 10-Sep-03 GMT is 09-Sep-03 in my timezone (US Central time). Can you update the test to be a little more

[jira] Commented: (SCM-120) ClearCase Changelog test failure

2006-01-03 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-120?page=comments#action_54812 ] mike perham commented on SCM-120: - This fixes the problem: Index: src/test/java/org/apache/maven/scm/provider/clearcase/command/changelog/ClearCaseChangeLogCommandTest.java

[jira] Commented: (SCM-121) Intermittent CVS test failures

2006-01-03 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-121?page=comments#action_54813 ] mike perham commented on SCM-121: - I fixed the test failure reported by Dennis above. There are still failures in the Diff TCK test case. I can't figure out why they are breaking

[jira] Assigned: (SCM-120) ClearCase Changelog test failure

2006-01-04 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-120?page=all ] mike perham reassigned SCM-120: --- Assign To: mike perham > ClearCase Changelog test failure > > > Key: SCM-120 > URL: http://jira.code

[jira] Resolved: (SCM-120) ClearCase Changelog test failure

2006-01-04 Thread mike perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-120?page=all ] mike perham resolved SCM-120: - Resolution: Fixed Patch applied. > ClearCase Changelog test failure > > > Key: SCM-120 >

[jira] Commented: (SCM-114) Clientspec naming

2006-01-16 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_56016 ] Mike Perham commented on SCM-114: - Currently I am leaning towards: {noformat} ${user}-${host}-MavenSCM-${check_out_path} For example: mike-buildmachine-MavenSCM-/tmp/continuum/work/16

[jira] Created: (SCM-133) Merge redundant repository classes

2006-01-16 Thread Mike Perham (JIRA)
Merge redundant repository classes -- Key: SCM-133 URL: http://jira.codehaus.org/browse/SCM-133 Project: Maven SCM Type: Improvement Components: maven-scm-api Versions: 1.0-beta-2 Reporter: Mike Perham Fix For

[jira] Resolved: (SCM-113) Support persistent and transient clientspecs

2006-01-16 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-113?page=all ] Mike Perham resolved SCM-113: - Resolution: Fixed Added ScmProviderRepository.setPersistCheckout(boolean) which applications can use as a hint to the SCM provider. Also added a

[jira] Resolved: (SCM-114) Clientspec naming

2006-01-16 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-114?page=all ] Mike Perham resolved SCM-114: - Resolution: Fixed Added path to clientspec name. Also added owner as a field since it was creating clientspecs without an owner before (I assumed it would associate

[jira] Commented: (SCM-154) Bazaar tests should not assume bzr is installed

2006-02-07 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-154?page=comments#action_58070 ] Mike Perham commented on SCM-154: - cvs and svn are usually already installed on any open source developer's machine. bzr is not. Thus it is bzr that really presents the firs

[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59326 ] Mike Perham commented on SCM-165: - John, please attach a standard SVN diff. Your diff does not contain the filename headers. svn diff > patch.diff > PerforceChangeLogCommand ne

[jira] Assigned: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-165?page=all ] Mike Perham reassigned SCM-165: --- Assign To: Mike Perham > PerforceChangeLogCommand needs to use the same clientspec as the update > c

[jira] Assigned: (SCM-163) PerforceUpdateCommand does not correctly return change list

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-163?page=all ] Mike Perham reassigned SCM-163: --- Assign To: Mike Perham > PerforceUpdateCommand does not correctly return change list > --- > >

[jira] Resolved: (SCM-163) PerforceUpdateCommand does not correctly return change list

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-163?page=all ] Mike Perham resolved SCM-163: - Resolution: Fixed > PerforceUpdateCommand does not correctly return change list > --- > >

[jira] Commented: (SCM-163) PerforceUpdateCommand does not correctly return change list

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-163?page=comments#action_59327 ] Mike Perham commented on SCM-163: - Thanks for tracking this down, John. The code was written before the changelog command was well defined. > PerforceUpdateCommand does not correc

[jira] Resolved: (SCM-164) PerforceUpdateCommand fails with NPE

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-164?page=all ] Mike Perham resolved SCM-164: - Resolution: Fixed Fix Version: 1.0-beta-3 > PerforceUpdateCommand fails with NPE > > > Key: SCM-164 &g

[jira] Updated: (SCM-163) PerforceUpdateCommand does not correctly return change list

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-163?page=all ] Mike Perham updated SCM-163: Fix Version: 1.0-beta-3 > PerforceUpdateCommand does not correctly return change list > --- > >

[jira] Assigned: (SCM-164) PerforceUpdateCommand fails with NPE

2006-02-23 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-164?page=all ] Mike Perham reassigned SCM-164: --- Assign To: Mike Perham > PerforceUpdateCommand fails with NPE > > > Key: SCM-164 > URL: http://ji

[jira] Assigned: (SCM-168) PerforceChangeLogConsumer should use relative paths

2006-02-25 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-168?page=all ] Mike Perham reassigned SCM-168: --- Assign To: Mike Perham > PerforceChangeLogConsumer should use relative paths > --- > >

[jira] Commented: (SCM-168) PerforceChangeLogConsumer should use relative paths

2006-02-25 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-168?page=comments#action_59480 ] Mike Perham commented on SCM-168: - Are you diffing off of the maven 1.x SCM source code or an old beta or alpha, John? Your diff, while recognizable, does not match up with the latest

[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

2006-02-25 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59481 ] Mike Perham commented on SCM-165: - This patch fails when running the changelog command in standalone mode. Use the SCM plugin to run a changelog on some directory "mvn scm:chan

[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

2006-02-25 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59482 ] Mike Perham commented on SCM-165: - Would it be acceptable for me to set the clientspec in use as a system property or static variable and the changelog command would do the following

[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

2006-02-26 Thread Mike Perham (JIRA)
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59517 ] Mike Perham commented on SCM-165: - I don't see how I can make this work in all cases without forcing the user to provide a parameter or use something like the release.properties