On Thu, Mar 20, 2008 at 9:15 AM, murph. o. matic
<murph.o.matic_at_gmail.com> wrote:
> On Wed, Mar 19, 2008 at 6:22 PM, Mark Phippard <markphip_at_gmail.com>
> wrote:
>
>
> > Did you do Team > Share so that the project is connected to Subclipse?
> >
> > Mark
>
> No, I didn't. And I don't expect to need to, because this project is
> already connected to SVN on my other machine. Wouldn't reconnecting it
> cause some sort of weird collision when I commit my project files on
> this box, and then update on my other box? Where is the connection
> information stored?
When you install Subclipse, projects that are already in your
workspace are not automatically shared or connected with Subclipse.
The Team > Share option should detect the presence of the .svn folders
and just offer to connect it for you.
> Mark, the reason behind my questions has to do with some bizarre
> behavior I'm seeing while doing a build. When I do a build on the
> machine I'm having difficulties on, the /bin folder appears, the build
> works fine, but in addition to the usual /bin/com/domain/ ... directory
> tree containing my class files, I'm also seeing the every folder under
> /bin has .svn folders in it. These folders are not exact duplicates of
> the .svn folders in the /src tree, but for instance the entries files
> are exactly the same. The prop-base and text-base folders do not
> appear. Also, the timestamps on the .svn folders and files match the
> time of the build.
This is the behavior you get from the Eclipse build process when a
project is not connected with Subclipse. When it is connected,
Subclipse is able to mark those .svn folders as special so that
Eclipse knows to ignore them.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-03-20 21:25:25 CET