#509: Test compatibility with XMLRPC Plug-in
-----------------------+------------------------------
Reporter: mbooth | Owner: olemis
Type: task | Status: accepted
Priority: critical | Milestone:
Component: plugins | Version:
Resolution: | Keywords: rpc XmlRpcPlugin
-----------------------+------------------------------
Comment (by olemis):
Replying to [comment:5 mbooth]:
> So does this need fixing in Bloodhound or the plug-in?
>
Accurate answers will be available once a resolution is found . At least
for moment the I'm working on a fork of XmlRpcPlugin (namely BloodhoundRPC
plugin) . Depending on the nature of the changes needed , different things
might happen .
> If you need to patch the plug-in do you think it is feasible to make one
branch of code work in both Trac and Bloodhound/MultiProduct? (The
upstream maintainer may be more willing to take the patch...)
>
I'm co-maintainer of XmlRpcPlugin but I do not have commit access to
plugin's svn area @ t.h.o , only the maintainer . AFAICT , I'm not sure it
will be easy to push Bloodhound-specific patches to distribute them with
mainstream XmlRpcPlugin , at least until they prove to play nice with Trac
as well . But the fact is that e.g. the testing environment is completely
different , it's an extra maintenance overhead , etc ...
> Or will it be necessary to fork?
... so I just [https://bitbucket.org/olemis/bloodhound-rpc forked
XmlRpcPlugin @ Bitbucket] ;)
PS: We can try other alternatives later .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/509#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
