Description of problem:
xalan in F16 was built with openjdk-1.7.0, and any attempt to use it with openjdk-1.6.0 fails. There's still some discussion about whether openjdk-1.6.0 will be present in rawhide, but right now it's the only thing there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create foo.xml with contents:
<?xml version="1.0" ?>
2. Create foo.xsl with contents:
<?xml version="1.0" encoding="UTF-8"?>
3. /usr/lib/jvm/java-1.6.0/bin/java -cp $( build-classpath xalan-j2 xerces-j2 ) org.apache.xalan.xslt.Process -IN foo.xml -XSL foo.xsl
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/xalan/xslt/Process : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.security.AccessController.doPrivileged(Native Method)
Could not find the main class: org.apache.xalan.xslt.Process. Program will exit.
I'll let Andrew/Deepak chime in with their thoughts on OpenJDK 7.
This is going to happen for any applications built with 1.7, unless the explicitly build with target 1.6.
As for 1.7.0 not being in rawhide, it has been there for a while:
It's not that it's not in rawhide -- it's not in updates-testing. My F16 system is set up to look for packages in 3 locations:
I think this is pretty standard, since f16 is branched from rawhide already (please correct me if I'm wrong here). xalan-j2 already went into updates-testing, but openjdk 7 is not in any of those three repos yet. I can and have installed 7 from koji, but that's not the issue here. The issue is that unless openjdk 6 is going to be completely dropped, you can't build critical packages like xalan-j2 with target=1.7. It's going to make openjdk 6 useless.
I've posted to the devel list about this as well.
Ah, you mean it is not in F-16. Rawhide is different from F-16 now that they have branched.
Yes, there was a problem that caused it to not be on the repos. An update has been submitted for it though, and it has been marked stable. A soon as the system gets around to it, it should appear on the F-16 repos:
yikes, sorry, I did not realize that I had said rawhide. That was before my morning coffee. :-) I certainly meant F16; sorry for the confusion.
No problem. It seems like for now, rebuilding xalan might be the best thing while we work out the 1.6/1.7 situation.
I have expired the buildroot override for 1.7, so it should build with 1.6 again.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Note: as long as this is being rebuilt, it would be nice if it could include a POM files for each jar.
It doesn't look like xalan-j2 is built with Maven. Are you proposing injecting POMs from somewhere else? What about getting them into xalan upstream first?
Getting it from someplace like this is fine with me:
Note that maven2-common-poms currently contains
So for that POM I'm really asking that it be moved into the correct package.
There should also be POMs for
2) xsltc -- there's no upstream POM for this, but something like this is sufficient:
I'd love to see official POM files in upstream, but there are already several precedents in Fedora for shipping POMs for maven.org
I'm not a maven expert (nor am I the maintainer of xalan-j2) so I can't help with POM stuff. But I support all efforts with the Fedora Java stack :)
The original issue reported here was fix (xalan-j2 was rebuilt with jdk6). I'll open a separate issue with a patch for the pom addition.