Hi Mark,
I have the same problem with linked source folders (already under
svn). The problem (for me) is not, that subclipse does not support
version control for this folder. This could be done in the real source
folder. The problem is, that sublipse wants to delete all svn
informations. But it should simply ignore the linked folders and their
svn informations. I don't think this would conflict with the Eclipse
guideline.
Teddy
2007/7/27, Mark Phippard <markphip@gmail.com>:
> On 7/27/07, Robin de Silva Jayasinghe <robin.desilva@googlemail.com> wrote:
>
> > I do have an existing Eclipse project that mainly consists of the
> > .project and .classpath file (that I do not want to have under version
> > control) and a linked source folder that exists in a different
> > filesystem-location than the project itself. Those files
> > (Java-sources) are already a working copy of my SVN repository(have a
> > .svn directory). Sadly the Subclipse plugin does not seem to recognize
> > the files in Linked source folders. Am I right with this assumption?
>
> That is correct. The expected behavior for an Eclipse team provider
> that "supports" Linked Resources is to allow them to exist in a
> project, but not provide any version control support for them.
>
> See: "Strategies for Handling Linked Resources" in the Eclipse documentation:
>
> http://help.eclipse.org/help33/topic/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm
>
> --
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Nov 23 12:52:40 2007