But its related I think. Because modularisation will also enable us to provide separate artifacts for compilation dependencies of client code. This way you can tell your users to depend on the API and SPI artifact but not on any others. It would be crystal clear what is considered Cocoon internal and what not.
I remember a discussion about separate jars 3 or 4 month ago.
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106424060330963&w=2
-- Otego AG Tel: +41 (0)1 240 00 55 Giacomo Pati, CTO Mobile:+41 (0)79 262 21 04 Apache Software Foundation Member Mailto:[EMAIL PROTECTED] Hohlstrasse 216 Mailto:[EMAIL PROTECTED] CH-8004 Z�rich Web: http://www.otego.com
