My 2c is that integrated update/commit/setup is very important in a monotone eclipse plugin, but it depends what the focus of the tool is. If your goal is to provide useful integration for experienced monotone users, then yes, it is not very important.
However, a completely integrated SCM plugin that does not require the user to go to the command-line for everyday tasks can be a very important piece of getting an SCM tool accepted happily vs grudgingly in a mid to large-sized commercial development group. If that's not an important goal, it's fine, but I'm all for projects that pave the way for monotone's eventual world domination. Also, as for supporting renames - in response to somebody's comment - yes, in a mature project you don't do this all that much, but I would argue it is very important to support it for mature projects. Sometimes you really need to re-rationalize your package layout or rename a set of classes, and something like having to do the refactoring in eclipse and then do the manual renames in the CLI is exactly the the kind of thing that could keep you from doing it because it's just too much of a pain, even though you know it should be done. shawn _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
