Some more incoherent Saturday morning thinking.. %)
> dependencies for themselves; alternatively we could ship the QA'd jars in
> the lib directory - don't know what kind of license problems this might
..meaning:
- create new directory lib that contains all jars required for
cayenne-core and modeler at compile/run-time (i.e. for the distribution)
- keep jars required for tests, regression, ant tasks etc. in otherlib
- maybe move jars that are only required for examples into <example>/lib,
WEB-INF or whatever (struts, tapestry, ognl..)
We have to make it really, really clear what goes where and why.
-h
This archive was generated by hypermail 2.0.0 : Sat Apr 05 2003 - 05:45:57 EST