Community
Participate
Working Groups
Created attachment 208924 [details] output of be --repo http://bugs.bugseverywhere.org/ list --status=all --xml So, when bug 366925 has been closed, I continue my search for the solution of my problem of distributed issue tracking with Mylyn. There is a rather disheartening thread on http://stackoverflow.com/questions/3203272/distributed-issue-tracker-for-git-with-usable-eclipse-mylyn-support, and the only real path towards victory I found is https://github.com/mikegr/mylyn-ditz-connector, which is unfinished and abandoned by its maintainer (as is whole ditz project, it seems, http://article.gmane.org/gmane.comp.bug-tracking.ditz.general/548 notwithstanding). So, the only viable distributed issue tracker still standing seems to be Bugs Everywhere (http://bugseverywhere.org/ and https://gitorious.org/be/be). There are IMHO two possible ways of attack. First, --xml parameter to many commands makes be to output XML version of the output in their proprietary XML vocabulary (see attached output of be list --status=all --xml on the main BE repository). Another possibility is to use 'be share' mode where be works as a webserver expecting commands over HTTP in some kind of RESTful protocol which I was not able to decipher yet. Posting link to this bug to the development list in hope of getting more details.
First, let me point out that I'm a Bugs Everywhere developer with absolutely no experience with either eclipse or Mylyn. (In reply to comment #0) > the only real path towards victory I found is > https://github.com/mikegr/mylyn-ditz-connector, which is unfinished and > abandoned by its maintainer After a quick glance at this, I'm not sure if the auther got far enough to be worth copying. I can't find any code making external Ditz function calls, but perhaps I'm not looking in the right place. > There are IMHO two possible ways of attack. First, --xml parameter to many > commands makes be to output XML version of the output in their proprietary XML > vocabulary (see attached output of be list --status=all --xml on the main BE > repository). This is what I would do. However, repeated, external BE invocations might slow you down too much, since BE is no speed daemon to begin with. If you get this far, and repeated invocations are a problem, send another email to the BE list, and we could work on a command-level HTTP interface to BE. > Another possibility is to use 'be share' mode where be works as a webserver > expecting commands over HTTP in some kind of RESTful protocol which I was not > able to decipher yet. I think you mean `be serve`, which is probably not what you want. `be serve` exposes objects at the storage level (see `libbe.storage.base`). You're supposed to run it on a central server so that users (who probably don't have access to your projects versioned source) can work with a remote repository using a local copy of BE.
(In reply to comment #1) > After a quick glance at this, I'm not sure if the auther got far enough to be > worth copying. I can't find any code making external Ditz function calls, but > perhaps I'm not looking in the right place. I think he tried to parse YAML files (format of storage for ditz) directly, which seems to me quite crazy as YAML is not fully specified and different libraries can get different results from parsing.
Thanks for the suggestion. It does not fall into the core scope of the Mylyn project and we are unable to address it but we'll leave this request open to track community interest in this connector.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
