The reason is simple - the crimson parser bundled with the JDK's through 1.4.2(?) is complete crap. Additionally, even older JDK's don't have a parser bundled, which means you'd have to create multiple maven distros (one for parser-bundled JDKs and another which accounted for the xml parser). You're welcome to try to change the parser used by maven of course, but don't expect much in the way of support. These libraries are found in $MAVEN_HOME/lib/endorsed, and I believe they may be referenced specifically in the forehead.conf file in $MAVEN_HOME/bin (not sure about that, though).

One final thought: leaving the parser choice up to the user is the right thing to do when you're developing an application component which will run in some java context outside its own. However, this is an unnecessary and even undesirable level of flexibility for a standalone tool like maven. It only serves to make installation, configuration and [especially] support more complex.

Cheers,
john

Pak, Young-rok wrote:
it helps in some cases, but I still want to change xml parser for maven. I want to use 
JVM's default parser. why maven specifies XML Parser? I think this is bad. users must 
be able to choose their own parser without modifying maven script and classpath.

----- Original Message ----- From: "John Casey" <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, October 26, 2004 11:40 PM
Subject: Re: xerces




Yes, maven has an extdir that includes xerces-2.4.0 and xml-apis-1.0-b2.

You should try specifying 'maven.compile.fork=true' in your project.properties to see whether this helps. It should cause the javac execution to take place in a new process which is free of the maven version of xerces et al.

-j

St�phane Nicoll wrote:

Hello list,

In one of my project I use namely xerces-2.6.2, xalan-2.1.0 and xml-apis-2.0.0. It 
used to be an ant project which is compiling fine (SUN JDK 1.4.2). Now I moved to a 
maven project with exactly the same dependencies (I checked 3 times and even copy the 
lib from the ant project directly in my maven repo), I still have the same issue:

isXMLName(java.lang.String) in org.apache.xerces.dom.CoreDocumentImpl cannot be 
applied to (java.lang.String,boolean)

Having checked the API, it seems to be a change since xerces2 which I have. Putting my 
dependencies in IDEA and compiling just work fine, as my ant project. Is Maven using a 
given xerces version which is overiding my dependency somehow?

Regards,
St�phane


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to