Stephen McConnell wrote:
what does this do?

It a JNDI ObjectFactory that lets you access a new instance of the Merlin Kernel from a JNDI context.

so IIUC it is of no real use outside merlin?


I would like to change (or set up) informal sandbox policy: before
you put a new subproject in sandbox, write up a short proposal for
the subproject, so everyone knows the project is there and what it
does. And you'll have to lobby against a -1 of course.

I agree that new projects should be discussed before launching of on a sandbox commit. However, I do think that the notion of "project" should be qualified.

you have a suggestion? :D


If the structural breakout is problematic it could be repackage but
this would be nothing more that moving deck-chairs.

yes please :D


Makes things clearer.

it'd be my preference to keep all code used by one container inside a single base directory until it actually becomes used in another container. Like moving the phoenix dependencies into avalon-phoenix, merlin-jndi classes into avalon-sandbox/merlin, assembly classes into avalon-sandbox/merlin and container/lifecycle out of avalon-fortress (because it is in use in merlin).

This makes it clearer at a glance what the actual organisation of a project is. Another way to put it: consider the (hypothetical) case where we decide we're going to base "spearhead" on merlin/assembly. We might want an avalon-spearhead repository. Content of that as it stands now would be sandbox/assembly, sandbox/merlin-*, and I believe also sandbox/meta or sandbox/info.

All those packages are in fact a single "project". The fact they could be used independently of each other in theory doesn't change that. I can point at many packages in phoenix that are completely independent of everything else, for example.

The single thing that looks to be an exception (besides the merlin stuff in sandbox), instrument-*, is not! Just look at the gump dependency tree to see why :D

cheers!

- Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to