[jira] Created: (SCM-112) Broken links to mail-archives

Broken links to mail-archives - Key: SCM-112 URL: http://jira.codehaus.org/browse/SCM-112 Project: Maven SCM Type: Bug Reporter: Dennis Lundberg Priority: Minor Attachments: mail-archive.patch The links to the mail-archives are

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

[ 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't work at all > ---

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

perforce: checkout doesn't work at all -- Key: SCM-111 URL: http://jira.codehaus.org/browse/SCM-111 Project: Maven SCM Type: Bug Components: maven-scm-provider-perforce Versions: 1.0-beta-2 Environment: winX, maven 2,

[jira] Commented: (SCM-106) Validation of scm url fails because of ambiquities between source code and site documentation

[ http://jira.codehaus.org/browse/SCM-106?page=comments#action_53320 ] Dennis Lundberg commented on SCM-106: - A patch for the code is in the works. I thought that I would write a testcase for it as well, but am having trouble finding a good home for it.

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

[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53314 ] Jeff Jensen commented on SCM-110: - Gotcha. Good. So that also answers the other question - the scope impact of this change is only for this release situation (?). Nice. > Perforce sho

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

[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53307 ] Jeff Jensen commented on SCM-110: - Great idea! I wish I had thought of that ;-) I think that is a lot better - hard to find "perfect" with this situation, but some intelligence applied

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

[ 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/browse/SCM-110 > Projec

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

[ 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 hit

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

[ 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. O

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

[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53296 ] Jeff Jensen commented on SCM-110: - Thanks for explaining. So this -f occurs only in the release:perform, or elsewhere too? If not only with release:perforce, that is ugly; highly ineff

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

[ 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

[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53294 ] Jeff Jensen commented on SCM-110: - Would you mind explaining further please? mvn clean does not delete "source" files, only target files, so am wondering your premise. The only time I c

[jira] Commented: (SCM-108) JDK 1.5 code

[ http://jira.codehaus.org/browse/SCM-108?page=comments#action_53292 ] Dan Tran commented on SCM-108: -- I think this code went into maven-scm beta2, does it mean, we need jdk 1.5 to work with this version of SCM? > JDK 1.5 code > > > Key

[Fwd: Re: Perforce provider generates error]

--- Begin Message --- Thanks, Emmanuel I'm trying 1.0.2 today. The error I had previously is gone but I get another one: "Provider message: Unable to sync" which, probably, means that my p4 client is not configured correctly. Just to make sure that I'm doing the right thing here're my setting

[jira] Commented: (SCM-106) Validation of scm url fails because of ambiquities between source code and site documentation

[ http://jira.codehaus.org/browse/SCM-106?page=comments#action_53258 ] Emmanuel Venisse commented on SCM-106: -- I confirm it's a bug in code. After "scm", we should have ":" or "|". Documentation is correct. What do we need? - a patch for code - a pa

[jira] Closed: (SCM-107) [patch] additional info for specifying the clearcase viewstore

[ http://jira.codehaus.org/browse/SCM-107?page=all ] Emmanuel Venisse closed SCM-107: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-2 Applied. > [patch] additional info for specifying the clearcase viewstore > -