Leo Sutic wrote:
What I'd like to know is if this will lead to a dependencyMy initial impression is that the dependencies we would be looking at are basically at the core of the [clazz] package (not the reflection or attributes stuff). This means basically the org.apache.commons.clazz.* (i.e. none of the subpackages). Before conconsidering the framework relationship I think there is some validation/experimentation to be done - and yes, I agree that while clazz is evolving and in sandbox - its not a candidate for the framework. On the otherhand - I figure that working with the [clazz] project now is more likely to ensure it meets are needs and that [clazz] gets a shot in the arm though validation against real requirements.
on clazz for framework? I would be -1 on any such dependency,
especially while clazz is still very much growing in scope and dependencies itself.
Cheers, Steve.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
