so as not to break existing cvs module commit links, the CVS backend of VAPI should include a legacy 'cvs' menu path.

Comments

jpetso’s picture

Version: 5.x-0.9-rc5 » 5.x-1.0

The 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.

jpetso’s picture

Status: Active » Fixed

Commit 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.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.