Eclipse Community Forums: Rich Client Platform (RCP) » RCP project

Home » Eclipse Projects » Rich Client Platform (RCP) » RCP project - Multiple developers

RCP project - Multiple developers [message #464316]

Thu, 01 March 2007 23:59

Eclipse User

Originally posted by: partyhut.internode.on.net

Hi all,

I am not quite sure if this is the right place to ask this question but
since lots of you have real project experience, I hope you can shed some
light on this issue.

We are going to start a RCP project. The project is big and there will
be many programmers working on it. We are planing to use Eclipse with
CVS or SVN for source management. We are trying to allow people check
out as few files as possible (only files they need to change) and then
test the change against a central file repository. This will make sure
the change always work with the latest version of the system (other
people might change other subsystem anytime)... Is this achievable? If
yes, How do I setup eclipse and the project folder structure? Thank you
in advance.

Cheers,
Henry

Re: RCP project - Multiple developers [message #464323 is a reply to message #464316]

Fri, 02 March 2007 02:31

Eclipse User

HS wrote:

> Hi all,
>
> I am not quite sure if this is the right place to ask this question but
> since lots of you have real project experience, I hope you can shed some
> light on this issue.
>
> We are going to start a RCP project. The project is big and there will
> be many programmers working on it. We are planing to use Eclipse with
> CVS or SVN for source management. We are trying to allow people check
> out as few files as possible (only files they need to change) and then
> test the change against a central file repository. This will make sure
> the change always work with the latest version of the system (other
> people might change other subsystem anytime)... Is this achievable? If
> yes, How do I setup eclipse and the project folder structure? Thank you
> in advance.
>

Provided the pieces that your people will work on can be separated to
plug-ins - the whole process can be simplified: concrete developer is
working on a concrete plug-in without touching the whole system.

Anyway, assurance that people changes always work, and don't break the
whole system is achievable through using Unit Tests - there's nothing
to do with folder structure.

--
Michael

Re: RCP project - Multiple developers [message #464427 is a reply to message #464323]

Sun, 04 March 2007 18:37

Eclipse User

Originally posted by: partyhut.internode.on.net

Hi Michael,

Thank you for your prompt answer. I guess my real question is:

We will have multiple developers (1-3 ppl) work on each plug-ins and
plug-ins rely heavily on other plug-ins to work correctly. When
developing we would like to always test our work with the newest version
of other plug-ins constantly updated by other development group. It
would be great if our developers don't need to keep a local copy
(checked out from CVS) of the system as it might already changed. Also,
checking out every time before testing is painful. My knowledge of Unit
Testing is limited. I was thinking maybe all developers can test their
plug-in with a centralized copy of the latest system(from CVS) instead
of each one has a local copy of some old version. Any idea?

Cheers,
Henry

Michael Spector wrote:
> HS wrote:
>
>> Hi all,
>>
>> I am not quite sure if this is the right place to ask this question but
>> since lots of you have real project experience, I hope you can shed some
>> light on this issue.
>>
>> We are going to start a RCP project. The project is big and there will
>> be many programmers working on it. We are planing to use Eclipse with
>> CVS or SVN for source management. We are trying to allow people check
>> out as few files as possible (only files they need to change) and then
>> test the change against a central file repository. This will make sure
>> the change always work with the latest version of the system (other
>> people might change other subsystem anytime)... Is this achievable? If
>> yes, How do I setup eclipse and the project folder structure? Thank you
>> in advance.
>>
>
> Provided the pieces that your people will work on can be separated to
> plug-ins - the whole process can be simplified: concrete developer is
> working on a concrete plug-in without touching the whole system.
>
> Anyway, assurance that people changes always work, and don't break the
> whole system is achievable through using Unit Tests - there's nothing
> to do with folder structure.
>

Re: RCP project - Multiple developers [message #464437 is a reply to message #464427]

Mon, 05 March 2007 13:02

Eclipse User

HS wrote:

> Hi Michael,
>
> Thank you for your prompt answer. I guess my real question is:
>
> We will have multiple developers (1-3 ppl) work on each plug-ins and
> plug-ins rely heavily on other plug-ins to work correctly. When
> developing we would like to always test our work with the newest version
> of other plug-ins constantly updated by other development group.

I think a good technique may be:

1) Work on concrete module of the system, fix bugs, write Unit tests.
2) Update from CVS a local copy of the whole system.
3) Run Unit tests.
4) If there are failures (especially regression failures) - return to the
first step, otherwise - commit your changes.

> It
> would be great if our developers don't need to keep a local copy
> (checked out from CVS) of the system as it might already changed. Also,
> checking out every time before testing is painful. My knowledge of Unit
> Testing is limited. I was thinking maybe all developers can test their
> plug-in with a centralized copy of the latest system(from CVS) instead
> of each one has a local copy of some old version.
>

Then, you can run a nightly test on a centralized copy, if it's not critical
that untested code is committed...

--
Michael

Re: RCP project - Multiple developers [message #465172 is a reply to message #464437]

Sat, 24 March 2007 11:36

Eclipse User

Michael Spector schrieb:
> HS wrote:
>
>> Hi Michael,
>>
>> Thank you for your prompt answer. I guess my real question is:
>>
>> We will have multiple developers (1-3 ppl) work on each plug-ins and
>> plug-ins rely heavily on other plug-ins to work correctly. When
>> developing we would like to always test our work with the newest version
>> of other plug-ins constantly updated by other development group.
>
>
> I think a good technique may be:
>
> 1) Work on concrete module of the system, fix bugs, write Unit tests.
> 2) Update from CVS a local copy of the whole system.
> 3) Run Unit tests.
> 4) If there are failures (especially regression failures) - return to the
> first step, otherwise - commit your changes.
>
>> It
>> would be great if our developers don't need to keep a local copy
>> (checked out from CVS) of the system as it might already changed. Also,
>> checking out every time before testing is painful. My knowledge of Unit
>> Testing is limited. I was thinking maybe all developers can test their
>> plug-in with a centralized copy of the latest system(from CVS) instead
>> of each one has a local copy of some old version.
>>
>
> Then, you can run a nightly test on a centralized copy, if it's not critical
> that untested code is committed...
>

My suggestion is to let a programmer check out the minimal set of
required plugins needed to compile the plugin he is working on.
Next steps are writing code and unit tests as well as running them on
the minimal local plugin set.
In our team we are using cruisecontrol
(http://cruisecontrol.sourceforge.net/) for continuous integration of
the whole system. You can use cruiscontrol to run tests on the whole
system continuously and let the developers being notified via email or
html-interface if builds are failed or tests went wrong.

cheers
Armin

Previous Topic:	Antoher "unable to open editor, unknown ID" problem
Next Topic:	Access to PerspectiveBar?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 05 12:30:58 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter