| checking out all modules from a CVS server in one step [message #157151] |
Tue, 04 May 2004 07:18  |
Eclipse User |
|
|
|
Originally posted by: nagypal.web.de
Hi,
Is there a way to check out all of the modules of a CVS server into one
Eclipse project? The situation is the following: the KAON project on the
sourceforge server uses a directory structure, where each subcomponent
of the system is placed into a different source directory. These are
shown as modules in Eclipse. Theoretically it would be possible to check
out those modules one by one to an Eclipse project, although it is very
cumbersome, as there are quite a lot of them.
What is really problematic is that there are two files which are
"module-less", i.e. they are placed in the CVS root directory, as those
files are used by all of the modules. Eclipse gives me no possibility to
check out those files, there is a check out option only on directories.
With winCVS or a command-line CVS I can checkout all of the modules AND
those two files in one step by using e.g. cvs.exe -z 3
-d:ext:username@cvs.sourceforge.net:/cvsroot/kaon checkout .
But I cannot see how could I do something similar from Eclipse, and how
could I check out (and commit) those two files into the CVS root.
Any ideas? Thanks,
Gabor
|
|
|
|
| Re: checking out all modules from a CVS server in one step [message #157319 is a reply to message #157176] |
Wed, 05 May 2004 07:26  |
| Eclipse User |
|
|
|
Originally posted by: nagypal.web.de
Thank you for the hint, but it seems that this does not work. I tried to
do it on a CVS server where I have root access to edit the modules file.
The newly defined alias appeared in Eclipse, however I could not check
it out. In Eclipse 2.1.3 all of the options are greyed out except from
the "Check out module" one, and that one doesn't do anything. In Eclipse
M8 the "Check Put As" option is greyed out, which is a pity, because I
cannot control where Eclipse creates the project directory. Moreover,
choosing the "check out" option throws a CVS internal error.
I tried to check out the alisa module with a command line client, and it
worked as expected so I do not know why it isn't work under Eclipse.
But even if this solution would work, this would require a root access
to the CVS server which you normally do not have if it is an external
CVS server. It is strange that you have to change something on the
server to get a functionality which already exists in many of the CVS
clients (command line, WinCVS).
Rich Kulp wrote:
> You can update the CVSROOT/.modules files and use the -a option and
> create one big module that points to all of the other modules. Then when
> you check out that module it will check out the other modules specified.
>
>
|
|
|
| Re: checking out all modules from a CVS server in one step [message #157508 is a reply to message #157319] |
Thu, 06 May 2004 09:19 |
| Eclipse User |
|
|
|
Originally posted by: mailforgilbert.gmx.de
Hi,
we use the Team Project Sets for that purpose
This files with the ending *.psf have a structure like :
<?xml version="1.0" encoding="UTF-8"?>
<psf version="2.0">
<provider id="org.eclipse.team.cvs.core.cvsnature">
<project
reference=" 1.0,:pserver:servername:path_to_cvsrepo,Modulename,Module,ve rsion "/>
...
</psf>
the string after cvsrepopath describes
1. = name of project in your workspace (i always use the modulename)
2. = module in cvs u want to checkout
3. = optional versiontag, if there's no versiontag, u get always the
latest from head
You only need readaccess for the particular cvsrepository.
Then use Import | Team Project Set in your workspace and get all the
modules u entered in the *.psf-file.
Just consult the help of eclipse for Team Project Sets.
bye4now, Gilbert
Gabor Nagypal wrote:
> Thank you for the hint, but it seems that this does not work. I tried to
> do it on a CVS server where I have root access to edit the modules file.
[..]
> Rich Kulp wrote:
> > You can update the CVSROOT/.modules files and use the -a option and
> > create one big module that points to all of the other modules. Then when
> > you check out that module it will check out the other modules specified.
> >
> >
|
|
|
| Re: checking out all modules from a CVS server in one step [message #157694 is a reply to message #157508] |
Fri, 07 May 2004 04:21 |
| Eclipse User |
|
|
|
Originally posted by: nagypal.web.de
Hi,
Thank you, that way it really works! I could even check out all of the
modules in one step by setting the Modulename to ".". It is exactly what
I wanted!
Cheers,
Gabor
Gilbert Rebhan wrote:
> Hi,
>
> we use the Team Project Sets for that purpose
>
> This files with the ending *.psf have a structure like :
>
> <?xml version="1.0" encoding="UTF-8"?>
> <psf version="2.0">
> <provider id="org.eclipse.team.cvs.core.cvsnature">
> <project
> reference=" 1.0,:pserver:servername:path_to_cvsrepo,Modulename,Module,ve rsion "/>
> ..
> </psf>
>
> the string after cvsrepopath describes
> 1. = name of project in your workspace (i always use the modulename)
> 2. = module in cvs u want to checkout
> 3. = optional versiontag, if there's no versiontag, u get always the
> latest from head
>
> You only need readaccess for the particular cvsrepository.
>
> Then use Import | Team Project Set in your workspace and get all the
> modules u entered in the *.psf-file.
>
> Just consult the help of eclipse for Team Project Sets.
>
> bye4now, Gilbert
>
>
> Gabor Nagypal wrote:
>
>
>>Thank you for the hint, but it seems that this does not work. I tried to
>>do it on a CVS server where I have root access to edit the modules file.
>
>
> [..]
>
>
>
>>Rich Kulp wrote:
>>
>>>You can update the CVSROOT/.modules files and use the -a option and
>>>create one big module that points to all of the other modules. Then when
>>>you check out that module it will check out the other modules specified.
>>>
>>>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.34944 seconds
Home