When I build I get these errors:
[genlist] Generating information for Auto
org.xml.sax.SAXParseException: Invalid encoding
This was diagnosed as follows:
Fri May 24 03:13:14 2002
> Date: Fri, 24 May 2002 12:12:43 +0200
> From: Libor Kramolis <email@example.com>
> To: firstname.lastname@example.org
> CC: Michal Zlamal <email@example.com>
> Subject: Re: [nbdev] What with ANT?
> It looks Xerces is stricter than Crimson and
does not allow Java encodings
> (UTF8) if it is not explicitly set
I did not find who
> created XML document with UTF8 encoding but
Michal could know more about it.
> So there are two possibilities for
> - avoid creation of XML docs with UTF8
> - start parser with set allow-java-encodings
Can we please fix this soon?
These errors cause my build sub-targets to not
complete and get
redundantly revisited on every build.
I.e. I _think_ my builds would go faster if this
I found solution - I'll attach proposed patch. It is
workaround done with using reflection API.
Created attachment 5992 [details]
I applied suggested patch.
AFAIK "UTF8" really *is* an invalid encoding and no XML file should be
using it. They should be using "UTF-8". What file was using this
encoding?! I would recommend the patch be rolled back, the file with
the bogus encoding found, and the encoding declaration fixed to be
compliant to the XML standard.
Also who else gets this error? What is it about Ivan's build? Is there
some non-NetBeans module which includes the incorrect encoding
declaration in some XML file?
Do you guys have enough info? Do I need to provide more details?
And _yes_ I'd very much like to know why I"m suffering from this
and no-one else. In a related matter I also had my ant
problems (the "What with ant" theread) which only seemed to
I'm sorry Jesse to be unclear, the encoding used in
UpdateTracking task is UTF-8. I don't know why there is in
exception encoding name UTF8.
But the problem should be fixed. I tried nearly all
imaginalbe combinations of ANT and JDK and it was
I also tried ANT bundled with extra binaries.
Ivan: I think I don't need more informations. Please
verify if it is fixed.
And as a reply on your question: Nearly nobody are using
It works for me.