ubuntu-389-directory-server team mailing list archive
-
ubuntu-389-directory-server team
-
Mailing list archive
-
Message #00202
[Bug 1049671] Re: 389-admin-console : incompatible-java-bytecode-format with OpenJDK 7 as default-jdk
This bug was fixed in the package 389-admin-console - 1.1.8-1ubuntu1
---------------
389-admin-console (1.1.8-1ubuntu1) trusty; urgency=medium
* sync from unreleased debian git.
389-admin-console (1.1.8-2) UNRELEASED; urgency=low
* watch: Add a comment about the upstream git tree.
* control: Bump policy to 3.9.5.
* Use debhelper 9.
* control: Drop dependency on java runtime, it's not needed and can be
harmful. (LP: #1097283)
* rules: Use bytecode format 1.5. (LP: #1049671)
-- Timo Aaltonen <tjaalton@xxxxxxxxxx> Wed, 02 Apr 2014 16:19:08 +0300
** Changed in: 389-admin-console (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-admin-console in
Ubuntu.
https://bugs.launchpad.net/bugs/1049671
Title:
389-admin-console : incompatible-java-bytecode-format with OpenJDK 7
as default-jdk
Status in “389-admin-console” package in Ubuntu:
Fix Released
Bug description:
During a recent rebuild test it was detected that 389-admin-console builds Java bytecode
which is only compatible with Java >= 7.
The default-jdk in Ubuntu Quantal has been changed to OpenJDK 7 and all
packages that Build-Depend on default-jdk are being tested to ensure that
they produce bytecode which is backwards compatible with earlier versions
of Java.
https://wiki.ubuntu.com/JavaTeam/Java7Default contains more details on how
to resolve this issue and make sure that the Java bytecode built by this
package is compatible with earlier Java runtime environments.
Note that lintian in Ubuntu Quantal also contains a experimental check
which can detect this problem (incompatible-java-bytecode-format). Enable
this by using the -E flag when running lintian.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-admin-console/+bug/1049671/+subscriptions
References