Anyone using Mylyn? It seems like the next big thing to me. I have recently started creating branches to isolate features under development, and bug fixes from eachother... Mylyn claims to improve productivity by making "tasks" a first class object in your IDE, integrates with your bugtracker and version controller and you have a different "workspace" for each task, no more opening 20 explorer views at different points in the directory hierarchy
Eclipse + Zend both now have support. I will be testing it out soon, in the new Zend beta. I was wondering if anyone else has had experience with it or good word to put in
Mylyn
Moderator: General Moderators
Re: Mylyn
Admittedly, no. But I would like to check into it... I use Eclipse for all of my development, and I know I've seen the plugin(s) for it in there... maybe I should check it out nowjosh wrote:Anyone using Mylyn? It seems like the next big thing to me. I have recently started creating branches to isolate features under development, and bug fixes from eachother... Mylyn claims to improve productivity by making "tasks" a first class object in your IDE, integrates with your bugtracker and version controller and you have a different "workspace" for each task, no more opening 20 explorer views at different points in the directory hierarchy
Eclipse + Zend both now have support. I will be testing it out soon, in the new Zend beta. I was wondering if anyone else has had experience with it or good word to put in
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
Re: Mylyn
Looked at it, thanks for the link. 
Task contexts sound cool, although I was under the impression the contexts were generated automatically, by resolving dependencies or something, but after watching the video, it sounds as though you must manually add the nessecary modules to each task context.
I'm not as a solo developer contexts would save me much time. I know exactly where everything is instantly by looking at the class names and Eclipse already lets me instantly load a class dependecy by right clicking and clicking "Open Declaration" or pressing F3.
The bug tracking integration looks neat though.
Cheers,
Alex
Task contexts sound cool, although I was under the impression the contexts were generated automatically, by resolving dependencies or something, but after watching the video, it sounds as though you must manually add the nessecary modules to each task context.
I'm not as a solo developer contexts would save me much time. I know exactly where everything is instantly by looking at the class names and Eclipse already lets me instantly load a class dependecy by right clicking and clicking "Open Declaration" or pressing F3.
The bug tracking integration looks neat though.
Cheers,
Alex
Re: Mylyn
Well yeah theres jump to context but that solves a different problem, this saves the trouble of having click 20 times to "set up" your files/workspace, the same folders in your explorer view are expanded/collapsed as when you left the task. I just tried it out and its pretty useful. Its like "virtual desktops" in linux, except instead of virtual desktops you have tasks.
It is going to save me a fair amount of aggrivation, now my workflow is click task, (sometimes files will already be opened for me and my cursor right at the method declaration I need), then I fix the bug or issue or whatever, and can resolve the task right from my IDE, which automatically creates an SVN log message and closes the mantis bug for me.
I also finally figured out the mantis "roadmap" and "changelog" features, so this is going to be a huge reduction from my prev. workload which was to opena browser, search for & locate the bug, resolve it, copy & paste bug name into svn, copy & paste bug name & # into changelog, go back update the mantis issue with the revision #, and then I'd "close all" out of the files I was working on.
For me personally, especially when I'm working with unfamiliar code, I can easily have lots and lots of windows open. With this I could make tasks called "look at how the dispatcher works in this framework", and have maybe 5 or 6 windows there, create another task that "holds" 6 more windows (instead of having them all open at once and trying to find them).
Another problem is in layered software I might have
module1/foo
module2/foo
and my previous IDE would just show me "foo", "foo" for the tabs. Forced me to click thru my open windows to find whats what, anything that cuts down all these daily nuisances is much welcomed in my book!
And it works like a feed, all your bug repositories from all over the net come into your little "inbox" grouped according to the queries and labels you created, so you can turn off those email notifications that are flooding your inbox that you delete anyways
It is going to save me a fair amount of aggrivation, now my workflow is click task, (sometimes files will already be opened for me and my cursor right at the method declaration I need), then I fix the bug or issue or whatever, and can resolve the task right from my IDE, which automatically creates an SVN log message and closes the mantis bug for me.
I also finally figured out the mantis "roadmap" and "changelog" features, so this is going to be a huge reduction from my prev. workload which was to opena browser, search for & locate the bug, resolve it, copy & paste bug name into svn, copy & paste bug name & # into changelog, go back update the mantis issue with the revision #, and then I'd "close all" out of the files I was working on.
For me personally, especially when I'm working with unfamiliar code, I can easily have lots and lots of windows open. With this I could make tasks called "look at how the dispatcher works in this framework", and have maybe 5 or 6 windows there, create another task that "holds" 6 more windows (instead of having them all open at once and trying to find them).
Another problem is in layered software I might have
module1/foo
module2/foo
and my previous IDE would just show me "foo", "foo" for the tabs. Forced me to click thru my open windows to find whats what, anything that cuts down all these daily nuisances is much welcomed in my book!
And it works like a feed, all your bug repositories from all over the net come into your little "inbox" grouped according to the queries and labels you created, so you can turn off those email notifications that are flooding your inbox that you delete anyways
Re: Mylyn
Branching vs non-branching discussion is split into its own thread: viewtopic.php?f=6&t=108435