i downloaded xalan 2.7.1 and discovered these specifications displayed in /META-INF/manifest.mf
Manifest-Version: 1.0 Created-By: 1.3.1 (IBM Corporation) Main-Class: org.apache.xalan.xslt.Process Class-Path: xercesImpl.jar xml-apis.jar serializer.jar Name: org/apache/xalan/ Comment: Main Xalan engine implementing TrAX/JAXP Specification-Title: Java API for XML Processing Specification-Vendor: Sun Microsystems Inc. Specification-Version: 1.3 Implementation-Title: org.apache.xalan Implementation-Version: 2.7.1 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xalan-j/dist/ Name: org/apache/xml/ Comment: DTM implementation and utilities Implementation-Title: org.apache.xml Implementation-Version: 2.7.1 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xalan-j/dist/ Name: org/apache/xpath/ Comment: XPath engine Implementation-Title: org.apache.xpath Implementation-Version: 2.7.1 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xalan-j/dist/ Created-By: 1.3.1 (IBM Corporation) --Created-By defines the version and the vendor of the java implementation on top of which this manifest file is generated. --This attribute is generated by the jar tool. Specification-Version: 1.3 --This attribute specifies the minimum extension specification version that is required by the applet. The Java Plug-in will compare the --value of this attribute with the Specification-Version attribute of the installed extension to determine if the extension is up to date. --and the applicable release notes for xalan 2.7.1 Xalan-Java 2.7.1 was released in August 2007. The serializer now has support for DOM Level 3 serialization (LSSerializer) for an XML parser. These changes are seen in the new class org.apache.xml.serializer.DOM3Serializer and the new package org.apache.xml.serializer.dom3 as well as a new method, asDOM3Serializer() on the older org.apache.xml.serializer.Serializer interface. More details are in the javadoc of those classes and interfaces. The distributions contain upgraded versions of xercesImpl.jar (Xerces-J 2.9.0) and xml-apis.jar (XML Commons External 1.3.04). The distributions were tested with these versions of Xerces-J and XML Commons External and are the recommended versions to use with the release. Important: You may experience unpredictable anomalies if your Xalan-Java and Xerces-Java builds are not in synch. so the only possible discontinuity i see is a possible version mismatch in the dependency tree e.g. xalan-version (2.7.1) != xercesImpl-version (2.9.0) != xml-commons-external (1.3.04) are there any testcases we can run which will identify the version mismatch ? Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > Subject: Ant 1.7.1, Xalan and Java 1.6.0_17 > Date: Fri, 7 May 2010 14:48:07 +0200 > From: juergen.knuple...@icongmbh.de > To: user@ant.apache.org > > Hello, > > > > I found out that the xalanimpl shipped with Ant1.7.1 is probably > incompatible to Java1.6.0_17, because > > > > Java1.6 is shipped with a different xalan version > > When I run Ant together with Java 1,6.0_17 I get a certain error > > When I remove xalanimpl in the ANT lib dir I don't get this error > > When I run this with Java1.5.0_16 I do not get this error > > > > So either the shipped xalan is buggy or incompatible or both. > > > > Is there already a common solution to solve this issue? > > > > I ask because I have a lot of builds. Some use Java 1.5 and some Java > 1.6. > > > > > > Regards Juergen > > > _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
