Your message dated Wed, 29 Oct 2008 21:47:38 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: dom4j: java bytecode / java runtime version mismatch
has caused the Debian Bug report #503778,
regarding dom4j: java bytecode / java runtime version mismatch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
503778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503778
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: dom4j
Version: 1.6.1+dfsg-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: jbc-mismatch

This package builds with openjdk-6 or cacao-oj6, which is not the
default jvm in testing/unstable. The openjdk-6 and cacao-oj6 javac
creates java bytecode for version 50, which cannot be used by older
jvms. Binary packages explicitely built with openjdk-6 or cacao-oj6
must not depend on java-runtime{,1,2,5}{,-headless}, but only on
java-runtime6{,-headless} or any of the non-virtual packages providing
a java6 runtime.

It is preferred to build the bytecode so that it runs on older jvms.
This is done passing '-source 1.[45]' to javac (or for cdbs ant tasks
setting ANT_OPTS to -Dant.build.javac.source=1.[45].

You usually can check for the java byte code with file(1), currently
broken in testing/unstable, or use javap -verbose (a script checking
the command line args (check-class-version) can be found at
http://people.debian.org/~doko/tmp/. Both .class and .jar files found
in the binary packages need to be checked.

Note: this report may be a false positive, if all bytecode files have
version 49 or less.



--- End Message ---
--- Begin Message ---
Matthias Klose wrote:
> Package: dom4j
> Version: 1.6.1+dfsg-3
> Severity: serious
> User: [EMAIL PROTECTED]
> Usertags: jbc-mismatch
> 
> This package builds with openjdk-6 or cacao-oj6, which is not the
> default jvm in testing/unstable. The openjdk-6 and cacao-oj6 javac
> creates java bytecode for version 50, which cannot be used by older
> jvms. Binary packages explicitely built with openjdk-6 or cacao-oj6
> must not depend on java-runtime{,1,2,5}{,-headless}, but only on
> java-runtime6{,-headless} or any of the non-virtual packages providing
> a java6 runtime.
> 
> It is preferred to build the bytecode so that it runs on older jvms.
> This is done passing '-source 1.[45]' to javac (or for cdbs ant tasks
> setting ANT_OPTS to -Dant.build.javac.source=1.[45].
> 
> You usually can check for the java byte code with file(1), currently
> broken in testing/unstable, or use javap -verbose (a script checking
> the command line args (check-class-version) can be found at
> http://people.debian.org/~doko/tmp/. Both .class and .jar files found
> in the binary packages need to be checked.
> 
> Note: this report may be a false positive, if all bytecode files have
> version 49 or less.

In the case of dom4j it appears to be a false positive:

[EMAIL PROTECTED]:~$ ./check-class-version /usr/share/java/dom4j-1.6.1.jar
dom4j-1.6.1.jar 47

dom4j-1.6.1.jar is the only JAR included, so I'm closing this bug.

Cheers,
        Moritz


--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Reply via email to