Re: Re: 'No such provider: perforce'

pom of release plugin is already updated. You must build it. Emmanuel dan tran a écrit : the current release plugin uses maven-scm alpha2. so you will need to fetch maven-release plugin, fix its pom to use maven-scm beta2 snapshot ( for now) -D On 11/23/05, *Wim Deblauwe* [EMAIL

RE: 'No such provider: perforce'

D:\apache\maven-scm\maven-scm-providers\maven-scm-provider-clearcase\src\main\java\org\apache\maven\scm\provider\clearcase\command\unedit\ClearCaseUnEditConsumer.java:[53,16] cannot resolve symbolsymbol : method contains (java.lang.String)location: class java.lang.String I think you are

Re: RE: 'No such provider: perforce'

I didn't see it, we must fix it Mike Perham a écrit : D:\apache\maven-scm\maven-scm-providers\maven-scm-provider-clearcase\src\main\java\org\apache\maven\ scm\provider\clearcase\command\unedit\ClearCaseUnEditConsumer.java:[53,16] cannot resolve symbol symbol : method contains

Re: 'No such provider: perforce'

Thanks, I added a JIRA ticket with a patch for it: http://jira.codehaus.org/browse/SCM-83 Wim2005/11/24, Mike Perham [EMAIL PROTECTED]:

[jira] Closed: (SCM-83) [patch] update to avoid that JDK 1.5 is needed to compile clearcase-provider

[ http://jira.codehaus.org/browse/SCM-83?page=all ] Emmanuel Venisse closed SCM-83: --- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-2 applied [patch] update to avoid that JDK 1.5 is needed to compile

problems with cvs provider

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

[jira] Created: (SCM-84) Develop VSS Provider for Maven-SCM

Develop VSS Provider for Maven-SCM -- Key: SCM-84 URL: http://jira.codehaus.org/browse/SCM-84 Project: Maven SCM Type: New Feature Components: maven-scm-provider-vss Reporter: George Gastaldi -- This message is

Clearcase unedit command

Can you remind me what is the role of this command for clearcase? Emmanuel

[jira] Commented: (SCM-84) Develop VSS Provider for Maven-SCM

[ http://jira.codehaus.org/browse/SCM-84?page=comments#action_51940 ] George Gastaldi commented on SCM-84: More info on VSS command (SS.exe) can be found on:

RE: Clearcase unedit command

Cool, but why do you force the user to do that? Shouldn't this operation just always be called and the svn/cvs impl be a no-op? -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 3:04 PM To: scm-dev@maven.apache.org Subject: Re:

Re: Clearcase unedit command

but we can perhaps add a hook in release plugin ( if clearcase or perforce, always set it to true) Emmanuel Mike Perham a écrit : Cool, but why do you force the user to do that? Shouldn't this operation just always be called and the svn/cvs impl be a no-op? -Original Message- From:

RE: Clearcase unedit command

I just tried this and I don't think it works correctly. Edit = please unlock and make this file available for me to change Unedit = please undo any of my changes, revert to repository version and lock it The PrepareReleaseMojo is just doing: 1. edit POM 2. update POM 3.

[jira] Commented: (SCM-80) [patch] update for the release and clearcase plugins

[ http://jira.codehaus.org/browse/SCM-80?page=comments#action_51971 ] Wim Deblauwe commented on SCM-80: - Ah, ok, I was not aware of that. Is there an easy way to get the list of the modified poms? How do you do this in SVN or CVS? [patch] update for the