Reported by مصطفی برمشوری, Jun 14, 2012
I`m intrested to create Indefero connector for Eclipse Mylyn. but i need help to organized Indefero API.
Comment 1 by مصطفی برمشوری, Jun 14, 2012
http://wiki.eclipse.org/index.php/Mylyn/Integrator_Reference is good place to start, but I`m good with eclipse and do not know about Indefero
Comment 2 by Thomas Keller, Jun 15, 2012
It seems as if the Task Integration for Mylyn seems to be a good starting point. We have a small REST-based API that could certainly extended to allow different kinds of actions, like authentication, CRUD and more. A small writeup what data are actually needed would be good (e.g. in our wiki), so we can check what we have and what is all missing... :)
Comment 3 by مصطفی برمشوری, Oct 28, 2012
Dear Thomas: First of all, I`m extremely grateful to you. Indefero is very good, easy to develop, and light tools. I reviewed Mylyn. The most important part of Mylyn, I suppose is good point to start, is Task API. This is organized to manage Issues. I`m familiar with Java and also Eclipse. So what can I do?
Comment 4 by Thomas Keller, Oct 30, 2012
Hi Maso! As I told you back in June it would be helpful to jot down the things Mylyn needs for its task integration, on a workflow, entity and field level. Most task trackers work more or less the same, but sometimes there are small subleties that could impose problems. It will be helpful for you to look at Indeferos database scheme in detail. The base issue type is (obviously) "idf_issues", while all issue comments (including the initial submission) are kept in "idf_issuecomments". "idf_issuefiles" holds meta data of uploaded files that are assigned to the individual comments. And finally "idf_issuerelations" are just that: they record "hard" bidirectional links between issues (opposed to "soft" links that are automatically created when you enter an issue ID like #123).