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"? My view would be that we have droids-core.jar, then a
jar for each 'component': droids-dynamics.jar, droids-xxx.jar etc.
Perhaps we have some bundled jars for the most common distributions:
droids-all.jar (includes everything in one jar)
Each component will need to provide its own set of documentation.
+ core
+ lib (logging and not much else)
Not sure about moving the lib dir into core, what are the benefits?
I'm just imagining a parallel structure to the components. Maybe dose
not matter. essentially the 'core' directory would look just like a
component directory, but only handle stuff for the core. It is just
taste...
+ src
+ java
+ test
+ plugins
droids/branch/LABS-144/depot/
I used the name depot (as suggested by you in another mail) for any
kind
of component. I like the association of both names to the real life.
In a "depot" you can find "components" that you use to build your
droid
(robot).
sounds good -- you can also find prebuild functional droids.
+ solr
IMO that has to be
org.apache.solr or org.apache.lucene.solr
Components should be named uniquely. Using package style naming seems
the most appropriate.
it seems a bit wordy to me. For clarity, I think a short unique name
is good. Essentially anything in our depot would have the package
prefix "org.apache.droids" so I'm not sure I see the bennifit of
naming the folders under depot with a fully qualified name.
Additionally, I don't think Droids (or any other project) should write
code in a package other then its own name. Code related to solr
should go in: o.a.droids.solr NOT org.apache.solr.droids. What if
solr wants to include droids code in their distribution? Do they have
to worry about a name conflict?
+ dynamics
+ src
+ lib
... (like the existing src/templates/component)
I am not sure I see dynamics more within each component rather then on
its own. I mean I expect e.g. a org.apache.solr.dynamic in the future.
Each component *may* depend on the 'dynamics' component -- if so, then
it adds configs/loading specific to itself.
But the 'dynamics' component is the one that contains all the common
code -- and the CLI you have...
ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
