When sharing common projects, there is not always a need for all users to
always have the svn metadata when they will not be committing any changes.
Exporting the entire parent directory and then importing the individual
projects into Eclipse is not a desirable workflow.
For one current, specific use case, I have several projects checked into
source control which are used as lab projects in a course I am developing.
Whether or not permissions are restricted in source control (in this case
they are), there is no need for the students to have the svn metadata.
Project checkouts would not be detrimental in this case, but exporting the
projects would be preferred.
On 11/5/07, Mark Phippard <markphip@gmail.com> wrote:
>
> On 11/5/07, Shelley <randomshelley@gmail.com> wrote:
> > Is there any way to export multiple projects from the SVN Repository
> View,
> > defaulting the export directory to the current workspace? I'd like to
> be
> > able to check out multiple clean projects using Subclipse (svn export),
> but
> > it looks like this can only be done one project at a time, it requires
> an
> > export directory to be specified, and the project is not exported as an
> > Eclipse project. It would be ideal if the "Export..." behavior was
> > identical to that of the "Checkout..." (perhaps just with an optional
> > additional "Export Directory" location, which defaults to the current
> > workspace).
>
> Why? What is the use case that you need to use Export to create
> Eclipse projects in your workspace? You could export a parent folder
> and then use Import existing projects into workspace.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
Received on Tue Nov 6 00:15:39 2007