Re: release plugin not providing file name
you can change it. Emmanuel Wim Deblauwe a écrit : Would that be yes to the first or the second question? 2005/11/23, Emmanuel Venisse [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Wim Deblauwe a écrit : Hi, the checkin command in the release plugin does not provide any file names in the ScmFileSet it passes. Can I change this to include pom.xml as a file name or will this break other SCM implementations? yes. It's kind of hard to say to clearcase: check in all files in this folder. I would first have to find out all checkout files myself, parse that output and check those files in. As you can understand, it would be easier to update the release plugin :) regards, Wim
Re: provider operations
Doc is actually only in ScmProvider javadoc. Status command returns the status of files in working copy, it's useful to 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 : Is there a high-level description of WHAT each operation is intended to provide? I'm trying to map Perforce onto these operations which were obviously designed for use with svn/cvs and struggling with the mismatches in the way the systems work. Mostly with update and status. Can someone in the know shed a little light on what these operations should do? mike
Re: release plugin not providing file name
I look at it later. Do you have test it too with a project with modules? Emmanuel Wim Deblauwe a écrit : ok, got it working completely. Patches are available: http://jira.codehaus.org/browse/SCM-80 What I did notice is that release.properties does not get deleted after the release:prepare has finished. Should users delete this by hand? regards, Wim 2005/11/23, Emmanuel Venisse [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: you can change it. Emmanuel Wim Deblauwe a écrit : Would that be yes to the first or the second question? 2005/11/23, Emmanuel Venisse [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Wim Deblauwe a écrit : Hi, the checkin command in the release plugin does not provide any file names in the ScmFileSet it passes. Can I change this to include pom.xml as a file name or will this break other SCM implementations? yes. It's kind of hard to say to clearcase: check in all files in this folder. I would first have to find out all checkout files myself, parse that output and check those files in. As you can understand, it would be easier to update the release plugin :) regards, Wim
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 I get the DefaultScmManager to see my new Perforce provider?mike
RE: 'No such provider: perforce'
Yes. I just noticed that at runtime mvn is using 1.0-alpha-2. The version I am working on is 1.0-beta-1-SNAPSHOT. How do I tell mvn to use my version? I tried 'mvn -U -up release:prepare' but it continues to use a2 instead of my newer snapshot. mike From: dan tran [mailto:[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 I get the DefaultScmManager to see my new Perforce provider?mike
