Jason van Zyl wrote: > Brett Porter wrote: > >> No, its for plugin shared library space: see >> <[EMAIL PROTECTED]> > > Can you guys please put stuff that is planned for the project in MPA. >
The vote was only on the 22nd. We can't have other tools supplant the mailing list as far fewer people follow it. Now that we've all discussed it, the action items should go in there, sure. > And what Fabrizio wants to work on falls into this pot? > As far as I understand, he wants to work on the plugin which is completely separate. If modifications are needed to the converter, then yes. >> I'm already done. > > You've setup the shared plugin shared library space? No, I created a converter component in /components/trunk like I said I was going to (And had planned to last week but got side tracked). > >> I'd rather not circumvent John's handling of the vote, >> and it would be good if that was eventually added there. It's over 72 >> hours, but we're probably just waiting for him to arise from Turkey coma. > > All right but what about tools in general what may or may not be used in > plugins. The conversion tool for example is something that would > definitely be used in/outside the context of a plugin. Well, I don't realy know any more. I've been working off the assumption anything not bundled in Maven goes there, but again this is pretty closely tied to the maven-model release so maybe its better off staying in /components. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
