| Beyond CVS [message #249894] |
Sat, 05 June 2004 14:50  |
Eclipse User |
|
|
|
Originally posted by: jeremy_caine.uk.ibm.com
The Ecipse project charter alludes to the VCM project - version and
configuration management, under the Platform sub project.
Drilling down to the Platform sub project, VCM seems to have turned into the
CVS client project.
Are there any plans to explore other VCM solutions beyond CVS e.g. an object
and package versioning repository similar to the Envy repos that use to be
part of VisualAge?
Thanks
|
|
|
| Re: Beyond CVS [message #250062 is a reply to message #249894] |
Mon, 07 June 2004 09:06  |
| Eclipse User |
|
|
|
It is a bit simplistic to say that the Team support has become a CVS
client project. In fact, the Team project is about exposing APIs so
that any repository provider can integrate into Eclipse, and there are
several examples of other clients using this support. See the Eclipse
ISV documentation for the details.
Another point, the Eclipse project currently has no mandate to develop
repository technology, and the focus so far as been supporting the
tooling required by the Eclipse development community, namely CVS. There
exists a technology project called Stellation that was supposed to
develop a versioning server, but the project is not very active these days.
Regards,
Jean-Michel
Jeremy Caine wrote:
> The Ecipse project charter alludes to the VCM project - version and
> configuration management, under the Platform sub project.
>
> Drilling down to the Platform sub project, VCM seems to have turned into the
> CVS client project.
>
> Are there any plans to explore other VCM solutions beyond CVS e.g. an object
> and package versioning repository similar to the Envy repos that use to be
> part of VisualAge?
>
> Thanks
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.10387 seconds
Home