I dug a bit more, and the only really big reason to keep Intake as a
fulcrum component is that Scarab, which is built on Fulcrum and T3,
has about a zillion lines (I think) of code that expects Fulcrum to
be org.apache.fulcrum... I'll look a bit more and see.
Eric
On Nov 2, 2005, at 11:49 AM, Thomas Vandahl wrote:
Eric Pugh wrote:
1) Move parser classes to Fulcrum-Parsers, and rejuvenate that
project.
2) Move parser classes to a seperate Turbine sub component, and
let that build and have both Turbine and Intake depend on that.
3) Move Intake back into the Turbine project as a sub component,
and not have it be a Fulcrum component, but still deal with 1 or 2.
I'd go for 3) at the moment. Though Intake may be a valuable
standalone component, it is very much Turbine centric right now.
IMHO it is always possible to duplicate the few relevant classes in
both code trees. Their code is fairly static anyway, so it's not a
big maintenance issue.
Bye, Thomas.
---------------------------------------------------------------------
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]
