Hi Chad,
thanks heaps for your reply. I have looked into the svn:externals and they
are indeed exactly what I had in mind. In fact I have absolutely fallen in
love with them. They allow to 'attach' source from any repository location
to the src-folder of an eclipse project anywhere else in the repository :-)
I now see why subclipse doesn't support externals - there is no need for it,
indeed, subversion has solved this problem already.
cheers and thanks again,
Diego
_____
From: cebarne2@rockwellcollins.com [mailto:cebarne2@rockwellcollins.com]
Sent: Monday, 1 May 2006 10:15 PM
To: diego@tognola.net
Subject: RE: Subclipse and Linked Resources: No Team Integration
Hi Diego.
Looks like the preferred method of handling this is with svn:externals.
From what I gather on the mailing list, externals are handled pretty well by
Subclipse (and Tortoise). Much better than with straight command line. For
instance, committing the project root will recurse into the externals.
Using externals, you will be able to seperate your project from your source
in the repo. The project can simply have an svn:externals definition that
puts the source code where it needs to go in your eclipse project (during
checkout).
This is probably not a perfect solution, but should get you to a comfortable
place. Having said all that, I have not tried this myself, but other groups
here do use externals successfully.
Mark (markphip@tigris.org) from the Subclipse dev team broke the bad news
to me.
Good Luck
<mailto:cebarne2@rockwellcollins.com>
Chad Barnes | Common Development Environment | Rockwell Collins, Inc.
400 Collins Rd. NE | Cedar Rapids, Iowa 52498-0001 | USA
"Diego Tognola" <diego@tognola.net>
05/01/2006 09:16 AM
To
<cebarne2@rockwellcollins.com>
cc
Subject
RE: Subclipse and Linked Resources: No Team Integration
Hi Chad,
thanks for your summary. The consequences of this are very frustrating, I
must say.
1.) if I want to share a project via svn, then I have to put the source into
the project (as this is the only way of using subclipse in the working copy
of the project) --> the source location in the repository is strongly
coupled to the development environment !
2.) I can't create a second shared project that uses the same source.
In a professional development environment there are many reasons why source
and 'eclipse projects' should be located independently (automated builds,
the potentially large size of the source).
I will create a 'feature request' and hopefully someone from the subclipse
guys will have an open ear for these issues. I really hope that they are
experienced enough to realize that the advantages of enabling this feature
outnumber the disadvantages by far :-/
cheers,
Diego
P.S.: who from the Subclipse development team did you get the bad news from
? (maybe they'll accept volunteers to fix this issue ?)
________________________________
From: cebarne2@rockwellcollins.com [mailto:cebarne2@rockwellcollins.com]
Sent: Wednesday, 15 March 2006 8:44 PM
To: users@subclipse.tigris.org
Subject: Subclipse and Linked Resources: No Team Integration
Within a project, if a linked resource (a folder) is created
that
points to a folder in a different working copy, the Subclipse integration
does not recognize any resources within the linked resource as controlled by
SVN. To reproduce:
2 Working copies on the filesystem:
(working copy "project)
/workingcopies/project/
/workingcopies/project/.project
(working copy "TestFiles")
/workingcopies/TestFiles/Source/
/workingcopies/TestFiles/Source/file1.c
/workingcopies/TestFiles/Source/file2.c
/workingcopies/TestFiles/Includes/
/workingcopies/TestFiles/Includes/file1.h
Within Eclipse:
project/
src (linked to --> /workingcopies/TestFiles/Source)
inc (linked to -->
/workingcopies/TestFiles/Includes)
The point is, even though the project is controlled in
Subversion,
and the linked resources are controlled, Subclipse doesn't allow any SVN
operations on resources in the linked folders.
After investigating this problem, I received word from the
Subclipse
development team that this behavior is actually recommended by the Eclipse
API. I found this surprising as the ClearCase SCM Adapter I had been using
for IBM ClearCase integration does support linked resources. I suppose I
just expected all team integrations to work the same.
This feature will unlikely be added to the Subclipse plug-in
in the
future. In light of that, has anyone solved a problem like this in Eclipse?
Does Subclipse have good support for externals? Do recursive commits in
Subclipse commit the externals? Basically, I am looking for the downside.
Thanks to Mark for answering my initial questions.
Chad Barnes
Rockwell Collins, Inc.
Received on Tue May 2 08:25:37 2006