Closed (fixed)
Project:
Version Control API -- CVS backend
Version:
5.x-1.0
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
13 Jan 2008 at 04:55 UTC
Updated:
16 Jan 2009 at 17:40 UTC
so as not to break existing cvs module commit links, the CVS backend of VAPI should include a legacy 'cvs' menu path.
Comments
Comment #1
jpetso commentedThe largest part of this should probably be a patch for Commit Log to decouple commit constraints and HTTP request attributes. So Commit Log should be able to deliver a page just by calling commitlog_commits_page($constraints) (which is probably getting renamed to commitlog_page() later on) and reconstruct the attributes array after that. (The attributes array is required for the link to the RSS feed.)
Once that is done, a legacy menu path will only be an issue of parsing the request attributes into a different constraints array than Commit Log does natively.
Comment #2
jpetso commentedCommit Log 5.x-2.x has commit constraints and HTTP request attributes decoupled, as mentioned above. I just added a compatibility module (versioncontrol_cvslog_compat) to the CVS backend which implements the 'cvs' path on top of Version Control API, and redirects 'cvs-application' to 'versioncontrol/register'. So this issue is fixed now.