Steve Loughran wrote:
>
> Scot P. Floess wrote:
>>
>> so unless you are setting any kind of factory for the xml parser, it
>> should use the stock XML parser that comes with Java.
>>
>
> ant -diagnostics finds the XML parser
>
>
That's the problem. diagnostics ends with this
-------------------------------------------
XML Parser information
-------------------------------------------
Bad version number in .class file
so it never tells me where it's looking!
> Is there anything in your build.xml that is processing xml or you are
> setting the xml factory (off the top of my head I can't remember the
> factory name/property one sets to change the default)...
>
Not that I can see; it's the build file created by android. In any event,
when I run diagnostics, it should not be looking for a build.xml file, and
it still comes to a dead halt when trying to look for the XML parser. I
checked this by running the command
ant -diagnostics
from a directory that has no build.xml file at all, and it gave the same
output as in the original post.
Part of the build.xml file contains this:
<path id="android.antlibs">
<pathelement path="${sdk-location}/tools/lib/anttasks.jar" />
<pathelement path="${sdk-location}/tools/lib/sdklib.jar" />
<pathelement path="${sdk-location}/tools/lib/androidprefs.jar" />
<pathelement path="${sdk-location}/tools/lib/apkbuilder.jar" />
<pathelement path="${sdk-location}/tools/lib/jarutils.jar" />
</path>
--
View this message in context:
http://www.nabble.com/XML-Parser-give-%22bad-version-number-in-.class-file%22-tp24916911p24918193.html
Sent from the Ant - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
