[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-vcm-dev] The WVCM API
|
The only thing holding up the RI and TCK is getting someone to volunteer to
do the work (:-).
So there are two chunks of work that could reasonably be done by Eclipse to
"kickstart" the WVCM adoption process (i.e. to motivate vendors to implement
the API):
- implement an Eclipse Team Provider Plug-in based on the WVCM API
- implement the WVCM API on some freely available CM system (e.g. CVS).
The second chunk of work could then serve as a reasonable RI.
And if some automated tests have been developed for the second chunk of
work, that could serve as the basis for the TCK.
Cheers,
Geoff
-----Original Message-----
From: Jean-Michel Lemieux [mailto:Jean-Michel_Lemieux@xxxxxxxxxx]
> But if such a strong demand is identified, to make it happen, Eclipse
> would have to take responsibility for implementing an Eclipse plug-in and
> standard implementation of the JSR-147 API, since this is not
> something one is likely to get from elsewhere (e.g. a server vendor).
Have you considered developing the RI and TCK for JSR147 as Eclipse plugins?
Do you have any idea when the RI and TCK are planned?
One possibility for helping the Eclipse Team team adopt the WVCM would be to
have an Eclipse Team Provider plugin based on WVCM. This approach would help
you flush out any issues with the WVCM API and help us evaluate the
practicality of the API.
Cheers,
Jean-Michel
