> Andy Clark wrote:
> > What about introducing another target having dtd + schema support
> > without any WML/HTML DOM ? It would be useful to have another target for the
> > same for above mentioned reasons.
>
> This is becoming exponential. I think we should look into the
> Ant task (even if it's optional) that combines multiple Jar
> files into a single jar. We could then build separate jars for
> each module and the default target would combine them into the
> single jar file we have today.
+1. It would definitely add more flexibility.
This is what we have today...
TARGET --> DESCRIPTION
------------------------------------------------------
apijar --> generates the xmlParserAPIs.jar file"/>
dtdjars --> generates xercesImpl containing no schema support, xercesSamples
& xmlParserAPIs jars"/>
tinyjars --> generates xercesImpl with no schema support or HTML/WML DOM,
xercesSamples & xmlParserAPIs jars"/>
jar --> generates the xercesImpl.jar file"/>
deprecatedjar --> generates the xerces.jar file"/>
sampjar --> generates the xercesSamples.jar file"/>
jars --> generates xercesImpl, xercesSamples & xmlParserAPIs jars"/>
deprecatedjars --> generates xerces.jar and samples jar"/>
I think, we can have different modules like..
Only XNI Impl.
DTD -- XNI Impl + DTD specific stuff
DTD + Schema -- DTD + Schema specific stuff ( can we break here ? )
HTML -- HTML implementation
WML -- WML Implementation
Samples -- equivalent to "samjar"
Same can be done for xmlParserAPIs. Have separate jars for DOM,
SAX, JAXP , (XNI ??) and then default target that would combine them and produce
xmlParserAPIs.jar (DOM, SAX, JAXP)
Thanks,
Neeraj Bajaj
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
