> -----Original Message----- > From: Leo Simons [mailto:[EMAIL PROTECTED] > > > Yet another reason why I think issue tracking and roadmaps would help. > > The ASF might have a Jira installation as early as this week!
And I am eagerly awaiting the announcement. :) > > I brought this up because the new exporter component I put together for > > Merlin is a much needed feature (easy JNDI exporting of components. I > at > > least wanted something in place. I'll refactor it to the cornerstone > > package so as to maintain some consistency. > > its merlin-specific innit? (in that it only runs in merlin and is only > useful as 'part' of a container) > > if so, it might make sense to keep it with merlin. Good point. On the one hand, it's (currently) merlin specific. On the other hand, it's a component (extension), not integral to merlin itself. So it brings up similar issues as some of the excalibur code which is somewhere between component and container utility. Not sure where it should go which is why it's currently under the sandbox. The same goes for what's under the merlin-extensions directory still in the sandbox. It's other JMX, JNDI, and servlet stuff for merlin. Should merlin have its own spot for extensions under /avalon/merlin ? Should all of this utility code end up with excalibur (or wherever excalibur's final destination is)? jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
