Eclipse is deployed with CVS client plugin by default. Why there are no svn source control clients that are bundled also by default?
There's a discussion that sheds some light on potential problems integrating the various svn plug-ins that exist for eclipse.
From Tigris' Status of Eclipse SVN Proposal :
One final factor in this decision [to withdraw the proposal] was licensing. Any Subversion plug-in is going to depend on either Subversion's JavaHL library or the SVNKit pure Java library. SVNKit's license was rejected by Eclipse, and in the case of Subversion they were planning to review all the code before allowing us to use the library. Subversion has dependencies on libraries like Neon and BDB that have licenses that are not typically accepted by Eclipse. So we had some question as to whether we would be able to include JavaHL or SVNKit with our plug-in. Again, maybe this will turn out to not be an issue for Subversive.
So various licensing problems appears to be the crux of including an existing svn plug-in by default.
It probably has something to do with the fact that the source code for Eclipse itself is still stored in CVS.
© 2022 - 2024 — McMap. All rights reserved.