Keep a consistent API when plug-ins subclass/override Trac classes
|Reported by:||egilwilde||Owned by:||andreat|
I recently upgraded our Agilo installation to version 1.1.1. We soon found out that the upgrade broke the Mylyn connection to Eclipse, which we maintain using XML-RPC.
The cause seems to be that Agilo overrides the Milestone class with its own AgiloMilestone class. That caused the RPC namespace 'ticket.milestone' to change into 'ticket.agilomilestone', which in turn broke the Mylyn connection which relies on 'ticket.milestone.getAll'.
Now, I would not call this a bug in either product, but I think it is safe to assume that this is not the last case we will see of overriding classes in plug-ins. I would consider it a nice-to-have feature if the XML-RPC could be configured to provide a consistent API regardless of the names of the underlying implementing classes.
Change History (4)
comment:2 Changed 3 years ago by osimons
- Component changed from XmlRpcPlugin to AgiloForScrumPlugin
- Owner changed from osimons to andreat
comment:3 Changed 9 months ago by rjollos
- Resolution set to invalid
- Status changed from new to closed