[ http://issues.apache.org/jira/browse/XERCESJ-1119?page=all ]
Michael Glavassevich resolved XERCESJ-1119:
-------------------------------------------
Resolution: Fixed
This has nothing to do with which vendor's JDK is used to compile Xerces. The
comment about the xjavac task was out of date. This task is needed for
building on *any *JDK 1.4 and above to workaround the built-in parser APIs
which almost always clash with the current version of Xerces uses. You needed
to include xjavac.jar on your classpath though I admit that isn't obvious.
I've added a classpath to the taskdef so that the build.xml can be used without
needing to do that.
> Building with Sun JDK
> ---------------------
>
> Key: XERCESJ-1119
> URL: http://issues.apache.org/jira/browse/XERCESJ-1119
> Project: Xerces2-J
> Type: Improvement
> Components: Build
> Versions: 2.7.1
> Reporter: elharo
> Priority: Minor
>
> As shipped the build.xml file appears to require the IBM JDK and tools. i.e.
> this is found in the build.xml file
> <!-- enable compilation under IBM JDK 1.4 -->
> <taskdef name="xjavac" classname="org.apache.xerces.util.XJavac"/>
> and building produces:
> ~/tmp/xerces-2_7_1$ ant dtdjars
> Buildfile: build.xml
> BUILD FAILED
> /Users/elharo/tmp/xerces-2_7_1/build.xml:22: taskdef class
> org.apache.xerces.util.XJavac cannot be found
> I will eventually work my way around this one way or another. However, it
> should be possible to
> build Xerces from the source distribution without hacking the build file,
> installing the IBM JDK, reading the build file to find the right switches, or
> so forth.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
