Hi, I recently noticed a lot of duplicated effort in order to implement similar things in the eclipse and idea plugins. Downloading of source artifacts and javadocs has been reimplemented in the idea one, and I recently took off some bits of the custom artifact resolution used in the idea plugin and integrated it into the eclipse one.
It will probably be possible to share most of this stuff to reduce duplicate code and to improve consistency between plugins (use similar flags for common features and so on... reducing the numbers of "why the eclipse plugins does that and the idea one doesn't - or does that differently" questions from users). I've just committed some major changes to the eclipse plugin to change the artifact resolution behaviour (in order to avoid the need for installed reactor projects) and in the meanwhile I deeply refactored the plugin in order to extract a base mojo that could be useful for other similar plugins. The base mojo take care of artifact resolution, source and javadocs downloading, plus some basic messages and handling of common flags (download sources, directly link referenced projects...). The result is a list of dependencies in a "friendly format" for IDE mojos that can direcly be used to create configuration files. Probably also the source directories processing could be handled here (but not done yet). I would like to go on adding a few more fixes to the eclipse plugin and release a new version (probably the artifact resolution change worths a release on its own), but after that I would like to split all the generic stuff (currently in the org.apache.maven.plugins.ide package) in a shared library. Could this be interesting for idea plugins developers? (Brett?, Edwin?) Anybody likes this? fabrizio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
