Hey Carsten, On Wednesday 22 September 2010, CKoenig wrote: > can someone tell me if the agilomilestone completely replaces the > original trac milestone? (sorry, haven't looked into this in too much > detail yet)
You'll find this code in agilo/ticket/model.py. AgiloMilestone is a subclass of trac.ticket.model.Milestone, so it adds some behavior to Agilo's concept of Milestones. It also replaces the original trac milestone (monkey patching), so whenever you instantiate a trac.ticket.model.Milestone you actually get an AgiloMilestone. > At the moment I'm trying to write a fix - either to xmlrpc or to the > Mylyn Trac Connector, so they also work with the agilomilestone. > > The xmlrpc seems to be quite generic, so at the moment my guess is > that the Mylyn Trac Connector asks for the ticket.milestone.getAll > method via the RPC API. So it might be a good idea to change that > (essentially making the Trac Connector an Agilo Connector). Will have > a look into the Trac Connector sources later... I'm not sure what the problem actually is -- is the xmlrpc plugin trying to monkey-patch the milestone as well? Neither trac's version of it nor the AgiloMilestone have a getAll method. Sorry I can't be of more help, but I am not familiar with the Mylin or xmlrpc plugins. Cheers Robert -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agiloforscrum.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
