Andreas Hartmann wrote:
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
I changed this, now these steps use dedicated classpaths:
1. core API
2. core impl -> use core API
3. modules -> use core API
4. publications -> use core API + modules
-- 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]
