Configuring Project coming from SVN
We have a project in SVN we're converting to RTC.
Currently we have about 150 Eclipse Projects, P1 ... P150.
Each project is checked into SVN with its .project, .classpath, and of course the source files.
We structure SVN like so:
P1
trunk
files...
tags
T1
files...
T2
files...
branches
B1
files....
B2
files...
P2
etc.
When we want to do an integration, people responsible for each project "tag" each one, and then add that tag's name to an Eclipse ".psf" file. Projects that haven't changed keep their old tag name in the .psf file.
Then, to check out a particular integration, we use the .psf file to pull the exact set of SVN tags for each of the projects.
What's the best practice for doing this kind of thing in RTC?
-Marshall Schor
Currently we have about 150 Eclipse Projects, P1 ... P150.
Each project is checked into SVN with its .project, .classpath, and of course the source files.
We structure SVN like so:
P1
trunk
files...
tags
T1
files...
T2
files...
branches
B1
files....
B2
files...
P2
etc.
When we want to do an integration, people responsible for each project "tag" each one, and then add that tag's name to an Eclipse ".psf" file. Projects that haven't changed keep their old tag name in the .psf file.
Then, to check out a particular integration, we use the .psf file to pull the exact set of SVN tags for each of the projects.
What's the best practice for doing this kind of thing in RTC?
-Marshall Schor
2 answers
Instead of a .psf file, you would use an RTC stream.
When someone has changes that they want to make visible to the rest of
the team, instead of updating the .psf file, they would deliver their
changes to the RTC stream. Conversely, when you want to catch up to
the changes being made by other team members, you would accept changes
from stream (rather than pulling a set of tags).
Cheers,
Geoff
On 5/2/2011 5:38 PM, marshallschor wrote:
When someone has changes that they want to make visible to the rest of
the team, instead of updating the .psf file, they would deliver their
changes to the RTC stream. Conversely, when you want to catch up to
the changes being made by other team members, you would accept changes
from stream (rather than pulling a set of tags).
Cheers,
Geoff
On 5/2/2011 5:38 PM, marshallschor wrote:
We have a project in SVN we're converting to RTC.
Currently we have about 150 Eclipse Projects, P1 ... P150.
Each project is checked into SVN with its .project, .classpath, and of
course the source files.
We structure SVN like so:
P1
trunk
files...
tags
T1
files...
T2
files...
branches
B1
files....
B2
files...
P2
etc.
When we want to do an integration, people responsible for each project
"tag" each one, and then add that tag's name to an Eclipse
".psf" file. Projects that haven't changed keep their old
tag name in the .psf file.
Then, to check out a particular integration, we use the .psf file to
pull the exact set of SVN tags for each of the projects.
What's the best practice for doing this kind of thing in RTC?
-Marshall Schor