CVSModule_Compatibility missing component
rwilson16 - January 29, 2009 - 19:56
| Project: | Version Control API -- CVS backend |
| Version: | 6.x-1.0-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I can't get the full suite for the Version Control API to work, seemingly because the CVS.Module Compatibility function is missing a required module component. The package did not come with Versioncontrol_Project, which is required for the CVS.Module Compatibility to run.
#1
Fixed in commit 171685. The original intent was to enable the full functionality of cvs.module+Project*, but I figure this module might also make sense for sites that have no need for project node integration. (Btw, a beta version of versioncontrol_project does exist now, it just came a bit later than the other ones.)
#2
Automatically closed -- issue fixed for 2 weeks with no activity.