Hi Lenya devs, in order to achieve backwards compatibility and enforce better modularization, I'd suggest that we clearly separate the public Lenya API from internals which are subject to change.
For Java code, this could easily be achieved using different packages, for instance: public: org.apache.lenya.* internal: org.apache.lenyaimpl.* Dependencies between modules should also rely on public APIs. I don't yet know how this can be ensured, but I'm sure it can be done. Is there a related concept we could use for non-Java code, e.g., pipelines, XSLT, ...? -- 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]
