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