GOMEZ Henri wrote:
>
> More on the crimson build :
>
> You could find attached a diff (jax.par in crimson dir and
> java doc regenerated).
>
> The problem I've got is more conceptual than technical.
>
> When you package a RPM (maybe DEBIAN), you should allways
> your build from SOURCES.
>
> W
Hi Thomas,
Thanks for respond, I did solve my problem by using characters() and
LexicalHandler.startCData() and LexicalHandler.endCData() callbacks to collect
data that splits multiple lines in DATA content.
///
startCData(){
isCDATA = true;
}
characters(.)
{
More on the crimson build :
You could find attached a diff (jax.par in crimson dir and
java doc regenerated).
The problem I've got is more conceptual than technical.
When you package a RPM (maybe DEBIAN), you should allways
your build from SOURCES.
When you build xerces-j, all the sources are
Could you also include the build.xml ?
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-Original Message-
>From: Edwin Goei [mail