Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Linked resources and Version Control
Linked resources and Version Control [message #785736] Sun, 29 January 2012 06:42 Go to next message
Sergey L is currently offline Sergey L
Messages: 2
Registered: January 2012
Junior Member
Hi All!

We are working on IDE for the imperative structural language (with expressive power equivalent to C). We decided to choose Eclipse as the Platform. One of our challenges is that our customer has large code base written in this language and for him it is crucial that directory layout of the legacy code will be left untouched. In order to meet this requirement we were thinking about using linked resources (especially nice because its support in e4 is getting better). Our idea was to rely heavy on linked resources in order to use Eclipse IProject-related subsystem while leaving customer`s folder layout.

But it seems that CVS and SVN (subclipse) just ignores linked resources!

What are our options from here?

Maybe there is a version control system Eclipse plugin that works fine with linked resources?

We need to create modern full-blown IDE environment with refactoring, debugging etc, but what with source control?

Thanks in advance!
Re: Linked resources and Version Control [message #787720 is a reply to message #785736] Tue, 31 January 2012 17:34 Go to previous messageGo to next message
Brian de Alwis is currently offline Brian de Alwis
Messages: 242
Registered: July 2009
Senior Member
I think you'll need to file bugs against the relevant components. Include a detailed set of steps to demonstrate.
Re: Linked resources and Version Control [message #787916 is a reply to message #787720] Wed, 01 February 2012 00:35 Go to previous message
Sergey L is currently offline Sergey L
Messages: 2
Registered: January 2012
Junior Member
Actually, this is a recommended behaviour for the team providers:

Quote:
Strategies for Handling Linked Resources
In order to be "link friendly", a provider should allow projects with linked resources to be version controlled, but can disallow the version controlling of linked resources themselves.

A considerably more complex solution would be to allow the versioning of the actual linked resources, but this should be discouraged since it brings with it complex scenarios (e.g. the file may already be version controlled under a different project tree by another provider). Our recommendation therefore is to support version controlled projects which contain non-version controlled linked resources.

- taken from Eclipse help.

Now we have two ideas for the workaround:
(1) Implement the EFS extension for Eclipse - i.e. read some xml file with pathes and make them appear under our project as normal IFile`s.
2) Use external svn.exe in order to manipulate source control status of the linked resource files. This is closely to writing our own Subclipse, though.

Did someone tried (1), BTW? I mean - is it hard to write own file system extension?





Previous Topic:View disappears in one perspective if it is a fast view in another
Next Topic:Setting resource attributes not supported on Linux ppc64?
Goto Forum:
  


Current Time: Fri Jul 25 05:16:30 EDT 2014

Powered by FUDForum. Page generated in 0.06200 seconds