Maven 1

Problem with new XML APIs

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.1-beta-1
  • Component/s: None
  • Labels:
    None
  • Environment:
    Mac OS X 10.4.1
  • Number of attachments :
    0

Description

When compiling a class which makes a call to org.w3c.dom.Document.setXmlStandalone (part of the DOM Level 3 API, first packaged with J2SE 5.0) I am getting an error that javac cannot find the symbol setXmlStandalone(boolean). The error comes about because $MAVEN_HOME/lib/endorsed/xml-apis-1.0.b2.jar comes before the J2SE 5.0 classes.jar (on Mac OS X, usually rt.jar on other operating systems) on the classpath. This goes back to a problem of Maven using Xerces, which does not support the latest W3C spec.

A dirty dirty short-term fix that worked for me is to replace $MAVEN_HOME/lib/endorsed/xml-apis-1.0.b2.jar with a symbolic link to the classes.jar/rt.jar file.

Issue Links

Activity

Hide
Brett Porter added a comment -

1.1-beta-1 uses the JDK XML Parser. You can also remove the endorsed directory entirely in 1.0.2, the javax.* system properties in the startup script and the endorsed entries in forehead.conf.

Show
Brett Porter added a comment - 1.1-beta-1 uses the JDK XML Parser. You can also remove the endorsed directory entirely in 1.0.2, the javax.* system properties in the startup script and the endorsed entries in forehead.conf.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: