jtb version 1.4.4-1 failed to build with openjdk-7

Bug #888955 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jtb (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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

See attached log for full build failure details.

This log snippet might also be of interest:

            sb.append("// Please report to support : TODO $1 [ ?0 \".\" ?1 < IDENTIFIER > ]");
                                                               ^
EDU/purdue/jtb/visitor/AcceptInliner.java:536: error: unmappable character for encoding ASCII
            sb.append("// Please report to support : TODO $1 [ ?0 \".\" ?1 < IDENTIFIER > ]");
                                                                        ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:483: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. $1 [ ?0 "." ?1 < IDENTIFIER > ] )<br>
                             ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:483: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. $1 [ ?0 "." ?1 < IDENTIFIER > ] )<br>
                                    ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:499: error: unmappable character for encoding ASCII
    // .. .. . .. .. . .. $1 [ ?0 "." ?1 < IDENTIFIER > ] )
                               ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:499: error: unmappable character for encoding ASCII
    // .. .. . .. .. . .. $1 [ ?0 "." ?1 < IDENTIFIER > ] )
                                      ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:592: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. $2 [ ?0 ","<br>
                             ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:593: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. .. . ?1 [ IntegerLiteral() ] ] $3 "}" )?<br>
                             ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:606: error: unmappable character for encoding ASCII
    // .. .. . .. .. . .. $2 [ ?0 ","
                               ^
EDU/purdue/jtb/visitor/DepthFirstVoidVisitor.java:607: error: unmappable character for encoding ASCII
    // .. .. . .. .. . .. .. . ?1 [ IntegerLiteral() ] ] $3 "}" )?
                               ^
EDU/purdue/jtb/visitor/IRetArguVisitor.java:317: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. $1 [ ?0 "." ?1 < IDENTIFIER > ] )<br>
                             ^
EDU/purdue/jtb/visitor/IRetArguVisitor.java:317: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. $1 [ ?0 "." ?1 < IDENTIFIER > ] )<br>
                                    ^
EDU/purdue/jtb/visitor/IRetArguVisitor.java:394: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. $2 [ ?0 ","<br>
                             ^
EDU/purdue/jtb/visitor/IRetArguVisitor.java:395: error: unmappable character for encoding ASCII
   * .. .. . .. .. . .. .. . ?1 [ IntegerLiteral() ] ] $3 "}" )?<br>
                             ^
123 errors
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
────────────────────────────────────────────────────────────────────────────────
Build finished at 20111110-2016

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
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jtb - 1.4.4-1ubuntu1

---------------
jtb (1.4.4-1ubuntu1) precise; urgency=low

  * Fix FTBFS with OpenJDK7 (LP: #888955):
    - d/rules: Call jh_build with source/target 1.5 to ensure backwards
      compatibility and work around Java 7 encoding errors.
 -- James Page <email address hidden> Fri, 09 Dec 2011 14:48:27 +0000

Changed in jtb (Ubuntu):
status: New → 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.