CODEWITHSUNDEEP
eclipsesvn
theblitz
theblitz

Reputation: 6881

Eclipse and Collabnet Subversion

I have installed Collabnet Subversion on Eclipse in order to connect to out Collabnet server.

At present there is only one developer so there is not problem of clashing.

However, now we are adding multiple developers. Each one will be developing sections of one application. How do I organise the project? I can't have them checking out the whole project each time because they will lose any updates they have - if I am correct.

Should I split the aplication in such a way that each section is in a separate package. This way a programmer can import sections of the application that have been updated by another programmer without having to import the whole application each time.

Does that make any sense?

Upvotes: 0

Views: 714

Answers (1)

takteek
takteek

Reputation: 7110

I'm not sure I understand your problem. Each developer can just check out the whole project once. When they want to get changes that others have made, they run "update" and svn will replace/merge any modified files. There is no danger of losing changes. Even if multiple people edit the same file it will usually merge automatically, and if not, manual merge is available.

You should organize your application code by function. If this corresponds with "sections" that single developers will be working on, that's fine, but it's not absolutely necessary.

Upvotes: 3

Related Questions