Andreas Hartmann wrote:
Hi Lenya devs,
currently, it's not clear which classes+interfaces form
the Lenya API (i.e., have to stay backwards compatible
and therefore may be used by client code).
Examples are AbstractUsecase and DocumentUsecase:
Can you extend these classes without the danger of
incompatible changes in future 1.4.x versions?
I like the approach taken by Avalon/Excalibur:
- framework/api/src/java
- framework/api/src/test
- framework/impl/src/java
- framework/impl/src/test
I've started to separate the code and changed the build
process accordingly. Now, the code is compiled in this
order:
1. core API
2. modules
3. publications
4. core implementation
This has to be changed to a sophisticated dependency management,
i.e. if a module is compiled it should have to declare the
modules it depends on explicitely.
IMO publications shouldn't be allowed to contain Java code
at all so that they can be deployed at run-time, but this is
a different issue.
-- 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]
