On Oct 9, 2008, at 4:17 PM, Thorsten Scherler wrote:
On Thu, 2008-10-09 at 13:15 -0400, Ryan McKinley wrote:
root
+ tools
+ docs (generated docs -- for everything?)
For the core and core components (like dynamics) and our site.
is there a distinction between "core components" and just
"components"?
Core components are the basic/default implementation of a couple of
handler/protocols/... They can be reused in various use cases. May be
would be better to call them common components.
Thinking about it a bit more, I think we should expand 'core' to
include more common things -- including dependancies on httpclient and
perhaps a stax parser.
If that gets too unwieldy, then we can move 'common' things out later,
but right now it seem like it would be more trouble then it is worth
to break it down that much.
My view would be that we have droids-core.jar, then a
jar for each 'component': droids-dynamics.jar,
I agree to have a droids-core-dynamics.jar however this is for me
not a
component on its own. It is an dynamic extension of the core expressed
as conf.
http://ant.apache.org/ivy/history/latest-milestone/tutorial/conf.html
IIUC, components like tika/solr should not have any IOC (spring)
dependancy. However they can include some default configuration files
that the dynamics package knows how to deal with.
A package like "helloCrawler" could depend on droids-core, droids-
dynamics, and droids-tika -- it could use dynamics to wire everything
together...
Is that a reasonable understanding?
ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
