ClearCase 'checkout' implementation

2005-11-23 Thread Wim Deblauwe
Hi,

to make release:perform work on ClearCase we need to implement the
'checkout' command for ClearCase (this is not what ClearCase user would
call checkout!). As I understand it, 'checkout' should copy the files
(with a certain tag) from the source control system to a certain
directory and then the build should start on those files. So this is
what we need for ClearCase:

- create a view with a config spec: Since we need to look at a released
version and it has been labeled in release:prepare if all is ok, we
only need 1 line in the config spec, like this

ELEMENT * RLS_MYPROJECT_V1.0

- mount the correct vob. Don't know if this is really necessairy, the correct vob should normally already be mounted
- cd to the created view
- copy everything to a directory (or run the build from the newly created view?)

This is the commando's I think we will need to call:

// First create the view
cleartool mkview -tag maven_release_build_view \\MYCOMPUTER\cc_vws1\maven_release_build_view.vws
// Assign the correct config spec
[Create a temp file called configspec.txt with the config spec in it]
cleartool setcs -tag maven_release_build_view configspec.txt
[Following 2 lines maybe better left out for now]
cleartool umount -all
cleartool mount \my_own_vob

//Do the build here

//Call the following line after the build - If this is not possible to
call after the build, run it at the start of the next build
cleartool rmview -force -tag maven_release_build_view


anybody who agrees or disagrees, please comment!

regards,

Wim


Re: 'No such provider: perforce'

2005-11-23 Thread dan tran
best to checkout maven-scm source and build  
-D 
On 11/23/05, Mike Perham <[EMAIL PROTECTED]> wrote:

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 PM
To: 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



RE: 'No such provider: perforce'

2005-11-23 Thread Mike Perham



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


RE: provider operations

2005-11-23 Thread Jeff Jensen
LOL, yes, it does give the kitchen sink!  Opened may do all that you need.
If it does not give enough info, fstat can do all it does and more.

If all you need is an indicator of add/edit/delete/none of those, then
opened works well.  I'm glad that it seems you found what you are looking
for!  :-)


-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 23, 2005 7:19 PM
To: scm-dev@maven.apache.org
Subject: RE: provider operations

Jeff, yes but it seems like drinking from a firehose since it prints
everything about every file.  Even better IMO is the opened command.  I just
discovered it this evening and it appears to do everything the status
operation requires.

mike

-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 7:14 PM
To: scm-dev@maven.apache.org
Subject: RE: provider operations

Mike,

Are you aware of the fstat command?

Thankfully Perforce does not store that data locally, so it does not have to
traverse the local directory structure (slower 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 local metadata next to the files (a la
CVS or .svn) so it does not have easy or efficient support to say "give me
the status for all changed files below this directory".  It keeps that info
in one or more changelists associated with the user.  I will have to parse
those changelists, look for files whose location starts with the current
repository path and return those.

Update - that should be straightforward then.  It seems that Checkout and
Update are basically the same operation in Perforce.

Thanks for the explanation.
mike

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 4:37 AM
To: scm-dev@maven.apache.org
Subject: 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: 'No such provider: perforce'

2005-11-23 Thread dan tran
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: provider operations

2005-11-23 Thread Mike Perham
Jeff, yes but it seems like drinking from a firehose since it prints everything 
about every file.  Even better IMO is the opened command.  I just discovered it 
this evening and it appears to do everything the status operation requires.

mike

-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 23, 2005 7:14 PM
To: scm-dev@maven.apache.org
Subject: RE: provider operations

Mike,

Are you aware of the fstat command?

Thankfully Perforce does not store that data locally, so it does not have to 
traverse the local directory structure (slower 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 local metadata next to the files (a la CVS 
or .svn) so it does not have easy or efficient support to say "give me the 
status for all changed files below this directory".  It keeps that info in one 
or more changelists associated with the user.  I will have to parse those 
changelists, look for files whose location starts with the current repository 
path and return those.

Update - that should be straightforward then.  It seems that Checkout and 
Update are basically the same operation in Perforce.

Thanks for the explanation.
mike

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 4:37 AM
To: scm-dev@maven.apache.org
Subject: 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: provider operations

2005-11-23 Thread Jeff Jensen
Mike,

Are you aware of the fstat command?

Thankfully Perforce does not store that data locally, so it does not have to
traverse the local directory structure (slower 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 local metadata next to the files (a la
CVS or .svn) so it does not have easy or efficient support to say "give me
the status for all changed files below this directory".  It keeps that info
in one or more changelists associated with the user.  I will have to parse
those changelists, look for files whose location starts with the current
repository path and return those.

Update - that should be straightforward then.  It seems that Checkout and
Update are basically the same operation in Perforce.

Thanks for the explanation.
mike

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 4:37 AM
To: scm-dev@maven.apache.org
Subject: 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
> 
> 
> 




'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
Status - Perforce does not keep any local metadata next to the files (a la CVS 
or .svn) so it does not have easy or efficient support to say "give me the 
status for all changed files below this directory".  It keeps that info in one 
or more changelists associated with the user.  I will have to parse those 
changelists, look for files whose location starts with the current repository 
path and return those.

Update - that should be straightforward then.  It seems that Checkout and 
Update are basically the same operation in Perforce.

Thanks for the explanation.
mike

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 23, 2005 4:37 AM
To: scm-dev@maven.apache.org
Subject: 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

2005-11-23 Thread Emmanuel Venisse
no, it isn't removed by release plugin for the moment. release:prepare create it and release:perform 
use it.

When the release is terminate, you can remove it manually.

Do you have test release:perform with clearcase?

Emmanuel

Wim Deblauwe a écrit :

ok, cool.

What about that release.properties file? Should that be deleted normally 
by the release plugin?


Wim

2005/11/23, Emmanuel Venisse <[EMAIL PROTECTED] 
>:


ok, i'll try to test it

Wim Deblauwe a écrit :
 > no, I don't have such a project.
 >
 > 2005/11/23, Emmanuel Venisse <[EMAIL PROTECTED]

 > mailto:[EMAIL PROTECTED]>>>:
 >
 > 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]

 > >
 >  >  >>
 >  >  >  >
 > 
:
 >  >  >
 >  >  >
 >  >  >
 >  >  > 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: release plugin not providing file name

2005-11-23 Thread Wim Deblauwe
ok, cool.

What about that release.properties file? Should that be deleted normally by the release plugin?

Wim2005/11/23, Emmanuel Venisse <[EMAIL PROTECTED]>:
ok, i'll try to test itWim Deblauwe a écrit :> no, I don't have such a project.>> 2005/11/23, Emmanuel Venisse <[EMAIL PROTECTED]> [EMAIL PROTECTED]>>:>> 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]> 
[EMAIL PROTECTED]>>  > [EMAIL PROTECTED] [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]> [EMAIL PROTECTED]>>  >
[EMAIL PROTECTED] [EMAIL PROTECTED]>>>  >  >
[EMAIL PROTECTED] [EMAIL PROTECTED]>> [EMAIL PROTECTED]
 [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: release plugin not providing file name

2005-11-23 Thread Wim Deblauwe
no, I don't have such a project.2005/11/23, Emmanuel Venisse <[EMAIL PROTECTED]>:
I look at it later.Do you have test it too with a project with modules?EmmanuelWim 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]> [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]> [EMAIL PROTECTED]>>  > [EMAIL PROTECTED]
 [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: release plugin not providing file name

2005-11-23 Thread Emmanuel Venisse

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


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]

 > >>:
 >
 >
 >
 > 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: release plugin not providing file name

2005-11-23 Thread Wim Deblauwe
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,

Wim2005/11/23, Emmanuel Venisse <[EMAIL PROTECTED]>:
you can change it.EmmanuelWim Deblauwe a écrit :> Would that be yes to the first or the second question?>> 2005/11/23, Emmanuel Venisse <[EMAIL PROTECTED]
> [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>>


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

2005-11-23 Thread Wim Deblauwe (JIRA)
[patch] update for the release and clearcase plugins


 Key: SCM-80
 URL: http://jira.codehaus.org/browse/SCM-80
 Project: Maven SCM
Type: Task
Reporter: Wim Deblauwe
 Attachments: clearcase-release.patch, release.patch

These are 2 patches. One for the release plugin and one for the clearcase 
plugin to make the release:prepare goal work on clearcase. This has been tested 
on my machine and it works, so anybody else willing to test this is very 
welcome.

regards,

Wim

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



Re: provider operations

2005-11-23 Thread Emmanuel Venisse

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

2005-11-23 Thread Emmanuel Venisse

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




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: release plugin not providing file name

2005-11-23 Thread Wim Deblauwe
Would that be yes to the first or the second question?2005/11/23, Emmanuel Venisse <[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: release plugin not providing file name

2005-11-23 Thread Emmanuel Venisse



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




release plugin not providing file name

2005-11-23 Thread Wim Deblauwe
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?

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