Mark Phippard <markp@softlanding.com> wrote on 08/08/2006 12:22:02 PM:
> You could create a new folder in your repository. Call it "Eclipse
> Projects" or "IDE Projects" if you want to support multiple IDE's. Then
> store an empty pre-configured Eclipse Java project in this location.
This
> project would have this property set on its root:
>
> svn:externals ThirdParty url://server/repos/trunk/ThirdParty
>
> The project would have a src folder, and that folder would have this
> property:
>
> svn:externals Java url://server/repos/trunk/src/Java
> Images url://server/repos/trunk/src/Images
>
> Then your Eclipse developers just need to checkout this project and it
> will grab what they need automatically, and it will also be configured
> correctly for them.
A lot of the Subversion developers also recommend a similar technique with
a slight twist. I think the advantage is that it performs a lot better
than externals. In your case you would use all of the same concepts,
except you would commit an Eclipse project that contained this structure:
Project
|- src
|- Java
|- Images
|- ThirdParty
All of the folders would be empty. The developer would checkout this
skeleton project, and then select the individual folders and do Team ->
Switch to change them to the URL they wanted, such as
url://server/repos/trunk/src/Java or
url://server/repos/bramches/1.x/src/Java
It is a bit more work for the developer but it is also more flexible and I
think things like update/commit work a little better. I think it is also
easier to later "switch" a folder to a different branch or tag.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Tue Aug 8 18:33:37 2006