#509: Test compatibility with XMLRPC Plug-in -----------------------+------------------------------ Reporter: mbooth | Owner: mbooth Type: task | Status: review Priority: critical | Milestone: Component: plugins | Version: Resolution: | Keywords: rpc XmlRpcPlugin -----------------------+------------------------------ Changes (by olemis):
* status: accepted => review * owner: olemis => mbooth Comment: Hi Matt ! Replying to [comment:7 mbooth]: > Cool, thanks for your work on this. > > I'm actually okay with a fork as long as the XML-RPC API remains unchanged. There is already a lot of software out there that talks to Trac programatically and it would be great if it all could also talk to Bloodhound without change -- it would greatly lower the barrier to adoption :-) I have pushed some changes onto [https://bitbucket.org/olemis/bloodhound- rpc/src/8075ed8a7cd4?at=bloodhound_rpc bloodhound_rpc branch] in [https://bitbucket.org/olemis/bloodhound-rpc olemis/bloodhound-rpc repository @ Bitbucket] . All plugin tests are successful in my local working copy after applying the following patches (order matters). {{{#!sh $ hg qapplied t509/t509_r1477773_tracadmin_globalcmd_attr.diff t514/t514_r1477773_load_bootstrap_handler.diff t514/t514_r1477773_tracd_bootstrap.diff $ hg log -r qparent --template="[{svnrev}] - {desc}\n" [1480224] - Translate SELECT part of CREATE TABLE ... AS SELECT ... queries. Fixes an issue where some product plugin tables were prepopulated with rows from global product. }}} After reviewing [https://bitbucket.org/olemis/bloodhound- rpc/compare/bloodhound_rpc..#diff the differences] it is possible to realize that not much has changed in the plugin but there are subtle (backwards compatible) usage differences if running against product environments . Please review . -- Ticket URL: <https://issues.apache.org/bloodhound/ticket/509#comment:11> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound issue tracker