Hi, As you may already know I'm currently working on Ivybeans [1], a kind of IvyDE for Netbeans for which we have won a grant from Sun [2].
In this plugin I need to implement features very similar to what has been done in IvyDE, like code completion for Ivy files. I also need to implement some features which are not currently supported by IvyDE like settings files code completion, or a way to easily add dependencies to an existing Ivy file. These features are somewhat IDE agnostic (or at least can be based on common roots), and I think it would benefit both community and all users if we shared what can be shared. So I consider refactoring some code in IvyDE (especially code used for code completion) to make it reusable (actually I've already done the refactoring...). I'd move this code to a org.apache.ivyde.common package, which could be used by any IDE plugin developer. The next step would be to move this package in a separate module, so that other plugin developers can use it without embedding the whole eclipse plugin. Then I could add new features to this common package, which would ease the reuse of work I do for Netbeans plugin in eclipse plugin. So, do you think it makes sense to do that? Any objection? Xavier [1] http://code.google.com/p/ivybeans/ [2] http://www.netbeans.org/grant/ -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
