Hi Mark,
Thanks for your reply
Mark Phippard wrote:
> On Thu, May 8, 2008 at 8:04 AM, Johan Compagner <jcompagner_at_gmail.com> wrote:
>> i tried it once but that didnt work completely correct
>> but cant you just checkout the complete root
>> and then do File->Import and import the projects from that dir?
>
> I would make same suggestion.
We have been using subclipse .psf files as a means to distribute the
source code and set up the projects. It's a good way to manage a
consistent development setup, and is quite straightforward to use. You
are right, we could tell people to use an external svn tool to checkout
a working copy, then import it (effectively bypassing subclipse). But
then we'd have to scrap the .psf files which we like.
>> Currently i just use 2 workspaces.. 1 with the global checkout and 1 with
>> the imported from that other workspace.
>
> A long standing Subclipse problem has been that you cannot have nested
> projects in the same workspace. This would grind Eclipse to a halt as
> we refresh status information. This bug is fixed in the new version.
> I have been slowly working on a new 1.2.x release with some of these
> fixes, I just have not had enough time to really do proper testing and
> since Subclipse 1.2.x is supposed to be the stable release I am
> reluctant to put out a release I have not really tested.
>
> So I would just recommend using the latest 1.3.x release where this
> feature works fine.
Are you saying that we can already use nested subprojects in subclipse
1.3.x?
If so, how do I install 1.3.x, and what sort of time scales might these
features be introduced into a stable release (1.2.x or 1.4.x I assume)?
Thanks for your help,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-05-09 07:35:24 CEST