Community
Participate
Working Groups
CVS team information should be in a different feature than the workbench basics. Products built on Eclipse might not want to use CVS and might want to hide the team docs, or remove the team doc feature from a product build. Doc needs to be componentized or put in separate features in order to be flexible for products building on Eclipse.
As things currently stand, Team and CVS are not separate features so they always ships with the platform. If a decision was made to make it a separate feature than the doc would be separated as well but there is currently no plan to do this. Given that Team and CVS are capabilities that can be enabled/disabled, one could argue that perhaps the doc should be hidden/revealed in accordance with whether the capability is on or off. I'm copying Dejan in case he has any comments on this. Of course, the other problem is that RCP-based products are not being shipped on pieces of the platform. In this scenario, it is not so much about excluding Team/CVS as it is about including only those pieces that are relevant to the subset of the platform you are using.
I'm going to mark this is a dup of plan item bug 36964, which includes: "The Eclipse Platform help books should be restructured in a more modular manner by making better use of existing help system capabilities." There have been similar requests about the Ant/External tools documentation. *** This bug has been marked as a duplicate of 36964 ***
