Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: xom
-
Labels:None
-
Number of attachments :
Description
Jaxen seems to depend on the obsolete XOM 1.0:
http://cvs.jaxen.codehaus.org/browse/jaxen/jaxen/project.xml?r=1.70
This XOM release in turn depends on ICU4J 2.6.1. This is also obsolete:
http://icu.sourceforge.net/download/
and corrupt:
.../jdk6/bin/javap -classpath icu4j_2_6_1.jar com.ibm.icu.impl.data.LocaleElements_zh__PINYIN
java.lang.ClassFormatError: invalid constant type: 60
at sun.tools.javap.ClassData.readCP(ClassData.java:180)
[....]
XOM 1.1 does not appear to have this bad dep:
https://xom.dev.java.net/source/browse/xom/project.xml#rev1.2
Found when using a NetBeans development build with "Mevenide" Maven 2 integration on Hudson (dev.java.net) sources: transitive dependencies cause icu4j-2.6.1.jar to be scanned for code completion purposes, which writes an error to the log file due to the invalid class file.
None of this is Jaxen's problem. Jaxen deliberately supports XOM 1.0 or later. It does not require XOM 1.1 though it will work with it. Maven 1.0 does not allow us to say depends on 1.0 or 1.1. That's Maven's issue. We'll probably upgrade to Maven 2 that does allow us to do this next year, but not for the 1.1 release.
I don't know what's up with ICU4J, though I suspect it may be your bug, not theirs. (Try using a non-beta JDK to compile and see what happens.) However there's nothing Jaxen can do about that, regardless of where the source of that problem lies.