Home » Eclipse Projects » Technology Project and PMC » Automatic CVS checkout after installation
| Automatic CVS checkout after installation [message #67151] |
Fri, 06 May 2005 08:37  |
Eclipse User |
|
|
|
Originally posted by: daniel.eguest.net
Hello,
first, sorry for my poor English...
I want to ask if it's possible to check out some cvs projects after "the
installation" of eclipse.
If there are a lot of clients in a network, that have to be installed with
eclipse, you have to configure the cvs repository and checkout projects
manually. This need a lot of time! You can configure a workspace with the
metadata directory, that you can distribute to all clients, that have to
be installed. So the user have a cvs repository in eclipse and only has to
change the username and password. After that the user have to checkout
some cvs modules. That's not very user-friendly.
One idea is to display a screen where the user can enter his username and
password. After this preconfigured projects are checked out automatically.
Another idea, that I have, is to check out the projects with a read-only
user by the command line but then the workspace have to be automatically
refresh the new projects. I don't know if this is possible.
Hope you can understand my idea/problems.
Thanks a lot!
Bye
Daniel
|
|
|
| Re: Automatic CVS checkout after installation [message #67181 is a reply to message #67151] |
Sat, 14 May 2005 08:55  |
| Eclipse User |
|
|
|
The closest I can think of is currently a project set.
If you set up an initial workspace with a single project that contains a
project set, then people can use that project set to check out whatever you
specify in it.
When they choose to import based on the project set, it asks for their
user/password to the CVS.
My company uses the projectset ui plugin (which works pretty well) so devs
can open the project set file (psf) in the editor and choose what to import
or just pick "all".
Hope this helps!
-- Scott
"Daniel Engels" <daniel@eguest.net> wrote in message
news:bd02f11e4c1f0023cc6d47e5f85332ed$1@www.eclipse.org...
> Hello,
>
> first, sorry for my poor English...
>
> I want to ask if it's possible to check out some cvs projects after "the
> installation" of eclipse.
> If there are a lot of clients in a network, that have to be installed with
> eclipse, you have to configure the cvs repository and checkout projects
> manually. This need a lot of time! You can configure a workspace with the
> metadata directory, that you can distribute to all clients, that have to
> be installed. So the user have a cvs repository in eclipse and only has to
> change the username and password. After that the user have to checkout
> some cvs modules. That's not very user-friendly.
>
> One idea is to display a screen where the user can enter his username and
> password. After this preconfigured projects are checked out automatically.
> Another idea, that I have, is to check out the projects with a read-only
> user by the command line but then the workspace have to be automatically
> refresh the new projects. I don't know if this is possible.
>
> Hope you can understand my idea/problems.
>
> Thanks a lot!
>
> Bye
>
> Daniel
>
|
|
|
| Re: Automatic CVS checkout after installation [message #67192 is a reply to message #67181] |
Mon, 16 May 2005 05:48 |
| Eclipse User |
|
|
|
Originally posted by: thhal.mailblocks.com
Although project-sets are great, perhaps you need a bit more then that?
A project typically has dependencies to other projects or artifacts that
in turn have dependencies, in arbitrary depth. A mechanism that can use
this information and has the ability to materialize everything you need
into your workspace in collaboration with the team providers is
extremely useful.
A project that aims to provide this is currently being proposed to
Eclipse. Read more about it here:
http://www.eclipse.org/proposals/eclipse-buckminster
Kind regards,
Thomas Hallgren
Scott Stanchfield wrote:
> The closest I can think of is currently a project set.
>
> If you set up an initial workspace with a single project that contains a
> project set, then people can use that project set to check out whatever you
> specify in it.
>
> When they choose to import based on the project set, it asks for their
> user/password to the CVS.
>
> My company uses the projectset ui plugin (which works pretty well) so devs
> can open the project set file (psf) in the editor and choose what to import
> or just pick "all".
>
> Hope this helps!
> -- Scott
>
>
> "Daniel Engels" <daniel@eguest.net> wrote in message
> news:bd02f11e4c1f0023cc6d47e5f85332ed$1@www.eclipse.org...
>
>>Hello,
>>
>>first, sorry for my poor English...
>>
>>I want to ask if it's possible to check out some cvs projects after "the
>>installation" of eclipse.
>>If there are a lot of clients in a network, that have to be installed with
>>eclipse, you have to configure the cvs repository and checkout projects
>>manually. This need a lot of time! You can configure a workspace with the
>>metadata directory, that you can distribute to all clients, that have to
>>be installed. So the user have a cvs repository in eclipse and only has to
>>change the username and password. After that the user have to checkout
>>some cvs modules. That's not very user-friendly.
>>
>>One idea is to display a screen where the user can enter his username and
>>password. After this preconfigured projects are checked out automatically.
>>Another idea, that I have, is to check out the projects with a read-only
>>user by the command line but then the workspace have to be automatically
>>refresh the new projects. I don't know if this is possible.
>>
>>Hope you can understand my idea/problems.
>>
>>Thanks a lot!
>>
>>Bye
>>
>>Daniel
>>
>
>
>
|
|
|
| Re: Automatic CVS checkout after installation [message #598663 is a reply to message #67151] |
Sat, 14 May 2005 08:55 |
| Eclipse User |
|
|
|
The closest I can think of is currently a project set.
If you set up an initial workspace with a single project that contains a
project set, then people can use that project set to check out whatever you
specify in it.
When they choose to import based on the project set, it asks for their
user/password to the CVS.
My company uses the projectset ui plugin (which works pretty well) so devs
can open the project set file (psf) in the editor and choose what to import
or just pick "all".
Hope this helps!
-- Scott
"Daniel Engels" <daniel@eguest.net> wrote in message
news:bd02f11e4c1f0023cc6d47e5f85332ed$1@www.eclipse.org...
> Hello,
>
> first, sorry for my poor English...
>
> I want to ask if it's possible to check out some cvs projects after "the
> installation" of eclipse.
> If there are a lot of clients in a network, that have to be installed with
> eclipse, you have to configure the cvs repository and checkout projects
> manually. This need a lot of time! You can configure a workspace with the
> metadata directory, that you can distribute to all clients, that have to
> be installed. So the user have a cvs repository in eclipse and only has to
> change the username and password. After that the user have to checkout
> some cvs modules. That's not very user-friendly.
>
> One idea is to display a screen where the user can enter his username and
> password. After this preconfigured projects are checked out automatically.
> Another idea, that I have, is to check out the projects with a read-only
> user by the command line but then the workspace have to be automatically
> refresh the new projects. I don't know if this is possible.
>
> Hope you can understand my idea/problems.
>
> Thanks a lot!
>
> Bye
>
> Daniel
>
|
|
|
| Re: Automatic CVS checkout after installation [message #598673 is a reply to message #67181] |
Mon, 16 May 2005 05:48 |
| Eclipse User |
|
|
|
Although project-sets are great, perhaps you need a bit more then that?
A project typically has dependencies to other projects or artifacts that
in turn have dependencies, in arbitrary depth. A mechanism that can use
this information and has the ability to materialize everything you need
into your workspace in collaboration with the team providers is
extremely useful.
A project that aims to provide this is currently being proposed to
Eclipse. Read more about it here:
http://www.eclipse.org/proposals/eclipse-buckminster
Kind regards,
Thomas Hallgren
Scott Stanchfield wrote:
> The closest I can think of is currently a project set.
>
> If you set up an initial workspace with a single project that contains a
> project set, then people can use that project set to check out whatever you
> specify in it.
>
> When they choose to import based on the project set, it asks for their
> user/password to the CVS.
>
> My company uses the projectset ui plugin (which works pretty well) so devs
> can open the project set file (psf) in the editor and choose what to import
> or just pick "all".
>
> Hope this helps!
> -- Scott
>
>
> "Daniel Engels" <daniel@eguest.net> wrote in message
> news:bd02f11e4c1f0023cc6d47e5f85332ed$1@www.eclipse.org...
>
>>Hello,
>>
>>first, sorry for my poor English...
>>
>>I want to ask if it's possible to check out some cvs projects after "the
>>installation" of eclipse.
>>If there are a lot of clients in a network, that have to be installed with
>>eclipse, you have to configure the cvs repository and checkout projects
>>manually. This need a lot of time! You can configure a workspace with the
>>metadata directory, that you can distribute to all clients, that have to
>>be installed. So the user have a cvs repository in eclipse and only has to
>>change the username and password. After that the user have to checkout
>>some cvs modules. That's not very user-friendly.
>>
>>One idea is to display a screen where the user can enter his username and
>>password. After this preconfigured projects are checked out automatically.
>>Another idea, that I have, is to check out the projects with a read-only
>>user by the command line but then the workspace have to be automatically
>>refresh the new projects. I don't know if this is possible.
>>
>>Hope you can understand my idea/problems.
>>
>>Thanks a lot!
>>
>>Bye
>>
>>Daniel
>>
>
>
>
|
|
|
Goto Forum:
Current Time: Fri Oct 31 19:10:07 EDT 2025
Powered by FUDForum. Page generated in 0.05537 seconds |
Home