Michael Wechner wrote:
[...]
Yes, this is unfortunately still the case. I'm trying to remove
these dependencies, but maybe I've missed some.
For instance, the lucene module dependency still has to be removed.
what do you mean by removing these dependencies?
- eliminate all Java references to classes / interfaces declared in the module
- eliminate all sitemap references to components declared in the module
- ...
If the core needs search functionality, the search API has to be separated
from the module and added to the core (e.g., as a jar file).
Can you give an example, e.g. the repository layer?
The repository layer API (interfaces) would be part of the core
(if we keep the "core" concept). But the various implementations
of this API could live in modules. The core wouldn't depend on
these modules, it could be compiled independently.
but the running system would need at least one implementation ;-)
That's something different - that's not a dependency but a configuration
option. The core doesn't depend on a specific implementation. It's the
same as with JCR - you don't depend on Jackrabbit, or Jeceira, or ...
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
