I'm trying to figure out what the layout is/should be. I'm new to
ivy, so bear with me. Looks like we have:
<configurations>
<conf name="core"/>
<conf name="dynamics" extends="core" visibility="public"
description="dynamic support"/>
<conf name="plugins" extends="dynamics" visibility="public"
description="plugins support"/>
<conf name="robots" extends="dynamics" visibility="public"
description="plugins support"/>
<conf name="test" extends="core" visibility="private"
description="for testing our framework"/>
</configurations>
this implies plugins and robots extend dynamics.
If I understand 'dynamics' correctly, it is just a bunch of utilities
to help loading from spring. It also includes a command line
interface to start droids. Dynamics is nothing more then another
plugin.
About tests... I think each set of code should manage its own tests.
Perhaps it makes more sense for our layout to look like this:
root
+ tools
+ docs (generated docs -- for everything?)
+ core
+ lib (logging and not much else)
+ src
+ java
+ test
+ plugins
+ solr
+ src
+ lib
... (like the existing src/templates/component)
+ tika
+ src
+ lib
... (like the existing src/templates/component)
+ dynamics
+ src
+ lib
... (like the existing src/templates/component)
+ myCustomCrawler (hello crawler)
+ src
+ lib
... (like the existing src/templates/component)
Rather then "plugins" maybe we call them "contrib" or "extensions",
"ext"? I think I like "contrib"
Each contrib would manage its own dependancies -- it could depend on
'core' and other contribs.
Note, in this structure, there is no special 'robots' 'examples' or
'test' source tree. Everything would be a contrib.
I could make these changes to our branch, but doubt I could do it
without breaking the scripts...
thoughts?
ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
