Aleks,
Yes...I am trying to eliminate it from everything, including keel-container, mostly to reduce the JAR/war size. Our minimum requirement is JDK-1.4 which includes all the XML/XSL we need without relying on Xerces/Xalan. If you are running into issues, can you figure out which module has the dependency? If we must have it for some module, I'd much prefer to list a dependency in that module instead of keel-container, so only when using *that* module do we include Xerces in the final artifact.
if you say you wanted to "get rid of Xerces/Xalan from Keel", does this
include keel-container? When I did a full build yesterday I had an
unsatisfied dependency on xalan... I thought this was overseen so I
added it to project.xml and .classpath in keel-container. Was this
wrong? Sorry if it was!
Shash
http://keelframework.org/documentation.shtml Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
