Todo

Here are identified "must have" features. Please help me extend and prioritize this list use the Edit this page button in the end of the page to edit it. Add (Importance nn) where nn is a number from 1 to 10, where 1 is not important and 10 is drop your stuff an implement this first instead yo fu*king developer. Please change the importance as you want that is the idea with a wiki page.

Importance	Description	Tickets
Done	Pull/up couple, it's the closest thing to what CVS users know as a source update. (This need the original repository specified in "clone")	#18
7	Better Change log view	#27 #30
5	Merge with conflict resolution using the Eclipse structural diff.	#22
Done	Commit with history and a checked out files view	#24
4	Team operations	#18
4	Cherry picking, in a pull a list of all change sets on that remote repository that are not part of the local	#182
4	Hg tag
4	Better annotate view	#25
3	Documentation? with more screenshots
Done 0.1.134	Push, something CVS users don't have. It's the way to publish your changes back to the public server. (This need the original repository specified in "clone")	#18

Top problems

Here you can you top most annoying thing or missing feature with this plugin. Please do not be gentle, nothing but the naked truth is good enough. The rules are, only one entry per submitter, If I consider it fixed I will remove the entry and you can add a new one, you may change your entry if you like. All entrys must be tagged with a name, the name can be faked it you like. e.g. <name> : comment (The one named Zingo is mine)

• Zingo: The output in the console / dialogue box for annotate and change log sucks! Put it in a scrollable window ASAP!.
  • Thomas Waldmann: Seconded! :) Additionally, maybe add some "short log" that only shows 20 recent log entries, not everything.
• Thomas Waldmann: hg diff on a project does nothing. it should show the same stuff as "hg diff" on the cmdline in a scrollable window.
  • Zingo: log now works in 0.1.102 but it still not a scrollable window...
  • Markus Majer: Why not using the general diff gui of Eclipse for that? (example screenshot: http://www106.pair.com/rhp/eclipse-shots/eclipse-metacity-compare.png) It is used by many plugins, especially SCM plugins. Perhaps you could look at the source code of such projects to find out how to get a graphical output from a general diff output.
• Thomas Waldmann: I didn't find push/pull?
  • Fixed in 0.1.134 (Yes I know no update/merge yet...)
• Thomas Waldmann: I you change a file, it correctly labels it with M. If you take back the change and save again, it will still show the M label, even refresh does not make it go away. hg status doesn't show the file as M.
  • Zingo: Bug?
• halcyon: Checking out a project from CVS using the New Project Wizard: Import... Projects from CVS... (choose a project) Next... Check out as a project configured using the New Project Wizard... Finish. At this point the New Project Wizard comes up and you can select Java Project and do the rest of the project setup. There are a couple of ways around this, so it isn't a high priority: 1. version control the Eclipse .project file; when you import, Eclipse knows the type of project. 2. Clone the project on the command line, create a New Java Project from Existing Source, then do a Team... Share Project... select Mercurial, Next... Finish.
  • Actually, you could just use the clone/import wizard and creation/detection of a .project file will be done automatically. Afterwards you could just edit the project properties to your liking. Does this answer your use case?
• halcyon: The plugin allows you to Compare With... Parent Changeset (or any other, which is awesome), so I would like to be able to Replace With... Parent Changeset so that Mercurial no longer thinks the file has been modified. Again, this is something I use often in the CVS plugin, and I believe it simply deletes the file then updates it from the repository.
  • Try revert, this should do exactly what you want.

• <your name>: <Add your stuff to this page by using edit below, keep this line last>

Future Ideas

Here is a list of somewhat more wild ideas:

• Version sync:ing, e.g. I want the version in my eclipse plugin to have the same version as my latest commit to my repository.
• Make it possible to interface with Mylyn project to interface trac or other feature/bug systems like sourceforge, savana during check in so that one can get a list if "my assigned tickets/bugs" during check in to select for reference and auto bug close:ing. (see Mylyn project: http://www.eclipse.org/mylyn/ and http://wiki.eclipse.org/index.php/Mylyn_Integrator_Reference )
• Import and change a "alien" project, select a project in your HD (in the ultimate version also on the net) create a hg repository or hg clone it, then hg clone it again inte eclipse workspace where it setup as a project... During development you should update the original place with the latest version, and then from inside eclipse make a hg import of the mainstream changes, and also make it possible to supply patches from your changes. This should be a hacker dream, just download hack-away and produce a patch or re-sync easy.
• specifically my team needs/wants the equivalent of the CVS TeamSync? feature. Without that, I can't get buy-in for a cvs2hg switch.

Please add more... use Edit this page below.