-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all,
I have developed a few tools projects that I'm using to support multiple plugins, etc. I wanted to add the plugins to the mojo project, but I'm unsure of the proper place for these supporting projects. I'm not really inclined to add this type of project to the main maven project, since it really has very little to do with Maven itself, except tangentially. Besides, these sorts of projects should be available for development by the same group that maintains the mojo project, where the plugins themselves will eventually land. Specifically, the two projects I've developed are a RPM name-formatter utility and an Ant-task convenience API (sets up and manages the Project /Target instance used to programmatically use Ant tasks). The latter was factored out of the antrun plugin, and I'd like to eventually re-merge them, with the antrun plugin using the antcall (new) API...but that's up to Kenney. :) The RPM-naming utility is also used by an RPM artifact resolver, which I'm *really* unsure where to park. At any rate, I believe this problem isn't going to go away, and we need to address the question of supporting projects for mojos and other maven components. For this last item (components), it might not even make sense to house these projects in the mojo.codehaus.org project... Ideas? Thanks, - -john -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDZnvpK3h2CZwO/4URAi5HAJ0R62HYs+9OzbNhffkzPpFstSFuLACfWgvc WR9se5rIMfHM7QVVsimuM00= =qhsm -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
