Leo Simons wrote:
Farr, Aaron wrote:
I'll agree with the structural mess part, too. I'm hoping to help fix that.
Part of my problem is I don't want to overstep my bounds and start
re-organizing or refactoring things without a solid plan that (most)
everyone agrees on.
:D
Yet another reason why I think issue tracking and roadmaps would help.
The ASF might have a Jira installation as early as this week!
I posted a message to the list about a day ago summarising what is happening and some things we should be thinking about. If it doesn't show up later today I'll repost.
So how about I start working on [fixing cruft] and once the site is more presentable, I'll start bugging people about excalibur and cornerstone re-organization again. :)
sure thing. I have had a partial restructure of excalibur sitting locally here that I haven't had time to finish. I'll see if I can get that into a committable stage...
I also have a non-committed minor update to excalibur-lifecycle that I need to take care of (mavonization + impl/api split).
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)
Yes - well actually it's specific to the activation package - as distinct from Merlin which uses activation - which basically comes down to the same thing.
:-)
Steve.
if so, it might make sense to keep it with merlin.
cheers!
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
