Matt Cristantello <cristant@fstrf.org> wrote on 07/08/2004 02:52:02 PM:
> Here's what I'm trying to do:
>
> 1. Create a project and import it into subversion (outside eclipse,
> we're actually running a migration script from VSS to subversion).
> 2. Check out the files in the project to a shared network location.
> 3. Set up eclipse to use the shared network location as the project file
> directory.
> 4. Set up eclipse to share the project in the shared location into
> subversion for use in doing updates, commits, etc.
> 5. Repeat step 4 on multiple developers' PCs.
>
> I think the base of the problem is that I don't want to do an import
> after sharing the project -- I just want to share the project and then
> synchronize with the server. Subclipse seems to know what I want to do,
> as I get a prompt to synchronize with the server, unfortunately
> immediately after I click OK, the menu closes and the Team menu stays
> in its unconfigured state (share project, apply patch).
>
> Does that make more sense?
>
Not to me.
1. So your projects have already been places in the repository in this
step?
If that is the case, you ought to be just defining your SVN repository in
the SVN Perspective, you then browse the repository, pick your project and
do a Check out. This populates the workspace and has you all connected up
to go.
So you shouldn't need steps 2-5. The Team -> Share option is designed to
handle the scenario where you have created a brand new project in Eclipse
and want to add it to Subversion to place it under source control and so
other developers can then check it out to their workspace.
Subclipse is modelled after the CVS integration so the online help for CVS
within Eclipse would apply fairly well to Subclipse too.
Mark
Received on Fri Jul 9 04:56:43 2004