Stephan Beal wrote: > In principal, plain old transport is not the problem. The problem (as i > recall it, though it's been a while and i've got the memory of a goldfish) > was that i could not define a concrete structure for JSON/Ticket I/O > because tickets are customizable. Suggestions are of course welcomed, and > if there's a concrete case you or Eric have in mind, i can probably say > whether it's currently workable or estimate what it would take to make it > so.
If we assume for a moment that the user is willing to customize the Fossil ticket system to exactly match whatever is needed to integrate with JIRA, does the problem become easy overall? -- Eric A. Rubin-Smith Aterlo Networks, Inc. http://aterlo.com _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
