Am 08.09.2010 01:06, schrieb Charlie:
You just mustn't modify trac core, some plugins are not working with
Agilo but with Trac.
Unfortunately it's not that easy. While we try to maintain compatibility
with other plugins, Trac's structure makes it impossible to implement
certain features (ticket linking, fields per type, ...) without
influencing the core.
TracXmlRpc is even more a special case because it uses the class names
to generate it's API. We can't accomodate that while implementing the
features that make Agilo Agilo.
So unfortunately, I don't see a short-term solution here (besides
someone stepping up and adding some stuff to TracXmlRpc).
fs
--
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
