[capra-dev] Update site and stable version

[Jens Lideström <jens.lidestrom@xxxxxxxxxxx>]

Hello,

In ReqTool we need to be able to use a stable version of Capra that we
depend upon. If the development version of Capra change in an
incompatible way we need some time to get up to date.

The best way to achieve this would be to have an Eclipse update site
which we can use in our target platform definition file.

I have noticed that an update site is generated as a "build artifact"
in every Capra build for the build-src-develop-nightly job. It works
fine for us to use these update sites. But need to know that they
don't suddenly disappear.

We can see that the update sites are saved for all builds since the
beginning of the project. But maybe they need to be cleaned away
eventually. (Each build seem to generate 12 MB of data.)

 Can we agree on either:
* That the build artifact updates sites are not erased
* Or: That some specific ones of the update sites are preserved (in
the case of a cleanup)

Hans-Erik has looked around for a Hudson setting that lets us mark
certain build artifacts as "permanent" or something similar. He
believes these should be something like that but has not found it in
our Hudson configuration interface.

Jens Lideström
Software developer
rt-labs