libisrt-java version 4.8.20100629-1 failed to build with openjdk-7

Bug #888964 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libisrt-java (Ubuntu)
Fix Released
Undecided
James Page

Bug Description

During a rebuild test on precise with default-jdk switched to openjdk-7, a build failure was detected for libisrt-java version 4.8.20100629-1.

See attached log for full build failure details.

This log snippet might also be of interest:

                                                  ^
src/de/intarsys/tools/stream/StreamTools.java:161: warning: unmappable character for encoding ASCII
  * Parametern angegeben wurde. Fehler beim Schlie?en der Datenstr?me werden
                                                                  ^
Note: src/de/intarsys/tools/string/StringTools.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
11 warnings
find src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javadoc -classpath :debian/_jh_build.isrt -d debian/_jh_build.javadoc/api -quiet
Creating destination directory: "debian/_jh_build.javadoc/api/"
src/de/intarsys/tools/xml/EntityDecoder.java:34: error: unmappable character for encoding ASCII
     return "?";
             ^
src/de/intarsys/tools/xml/EntityDecoder.java:37: error: unmappable character for encoding ASCII
     return "?";
             ^
src/de/intarsys/tools/xml/EntityDecoder.java:40: error: unmappable character for encoding ASCII
     return "?";
             ^
src/de/intarsys/tools/xml/EntityDecoder.java:43: error: unmappable character for encoding ASCII
     return "?";
             ^
src/de/intarsys/tools/xml/EntityDecoder.java:46: error: unmappable character for encoding ASCII
     return "?";
             ^
src/de/intarsys/tools/xml/EntityDecoder.java:49: error: unmappable character for encoding ASCII
     return "?";
             ^
src/de/intarsys/tools/stream/StreamTools.java:159: error: unmappable character for encoding ASCII
  * Kopiert einen Eingabedatenstrom auf einen Ausgabedatenstrom. Anschlie?end
                                                                         ^
src/de/intarsys/tools/stream/StreamTools.java:160: error: unmappable character for encoding ASCII
  * (finally) werden die Datenstr?me geschlossen(!), sofern dies in den
                                 ^
src/de/intarsys/tools/stream/StreamTools.java:161: error: unmappable character for encoding ASCII
  * Parametern angegeben wurde. Fehler beim Schlie?en der Datenstr?me werden
                                                  ^
src/de/intarsys/tools/stream/StreamTools.java:161: error: unmappable character for encoding ASCII
  * Parametern angegeben wurde. Fehler beim Schlie?en der Datenstr?me werden
                                                                  ^
10 errors
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
────────────────────────────────────────────────────────────────────────────────
Build finished at 20111110-2017

Finished
────────

E: Build failure (dpkg-buildpackage died)

Revision history for this message
James Page (james-page) wrote : Build log
tags: added: amd64 auto java7-ftbfs
James Page (james-page)
tags: added: encoding
James Page (james-page)
Changed in libisrt-java (Ubuntu):
assignee: nobody → James Page (james-page)
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libisrt-java - 4.8.20100629-1ubuntu1

---------------
libisrt-java (4.8.20100629-1ubuntu1) precise; urgency=low

  * Fix FTBFS with OpenJDK7 (LP: #888964):
    - d/rules: Overide jh_build and pass source/target as 1.5 to ensure
      backwards compatibility and workaround Java 7 encoding errors.
 -- James Page <email address hidden> Wed, 14 Dec 2011 12:50:55 +0000

Changed in libisrt-java (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.