yea sounds good except I'll abbreviate "implementation" to "impl" so
the package names are reasonable.
Jim
On Jun 20, 2006, at 9:25 AM, Jeremy Boynes wrote:
Jim Marino wrote:
I'm leaning towards combining them because separating
commonalities out
into a third project is basically creating an "SPI2". Also, most
of the
stuff that would be pulled out is related to injection and
reflection
which I don't think we want to expose as an API at this point.
YAGNI? Fair enough.
We have "composite" and "system" sub-packages in core that
correspond to
implementation types - are you going to add "java" as third?
Should we add "implementation" as a parent package to all three?
I.e add
o.a.t.core.implementation.[system,composite,java]
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
