Why is crimson XML parser being used

Hello Robert,

Crimson XML parser was supplied with Java 1.4. Is it posible that build
agent started to use this Java? Could you please attach a build log to the
Jira request?

--
Pavel Sher

"Robert Gibson" <robbie_usenet@yahoo.co.uk> wrote in message
news:ei76ct$aef$1@is.intellij.net...

Help!
I'm trying to run some JUnit tests involving XML parsing and they are
systematically failing. Does anybody know why JUnit tests launched on from
a build agent should decide to use Apache crimson as the JAXP
implementation instead of the Sun-supplied Xerces? I can't find any jars
that contain crimson in my classpath or the agent's directories. (I'm
using JDK1.5 with the ipr runner and I'm forking JUnit once.)

>

I filed a bug
http://www.jetbrains.net/jira/browse/TW-1100
but I need to find a workaround ASAP.

>

Thanks for any help you can give,
R

Pavel Sher wrote:

Hello Robert,

Crimson XML parser was supplied with Java 1.4. Is it posible that build
agent started to use this Java?

I don't think so, I don't think I even have that JDK on the machine in
question.

Could you please attach a build log to the Jira request?

Done.

Thanks,
R

Hello,

According to attached build log runner used java from
/home/JavaLibs/PRODUCTION_LINKS/jdk/bin/java. It took this java because it
was specified in JAVA_HOME environment variable. What is the version of this
java?

--
Pavel Sher


"Robert Gibson" <robbie_usenet@yahoo.co.uk> wrote in message
news:ei7j2u$4if$1@is.intellij.net...

Pavel Sher wrote:

>> Hello Robert,
>>
>> Crimson XML parser was supplied with Java 1.4. Is it posible that build
>> agent started to use this Java?

I don't think so, I don't think I even have that JDK on the machine in
question.

>> Could you please attach a build log to the Jira request?

Done.

>

Thanks,
R

See my comments in the bug report - it turned out that the ipr runner is
using the CLASSPATH of the shell used to launch the agent. That's a bug,
right?
R