jbossas4 version 4.2.3.GA-6 failed to build with openjdk-7

Bug #888943 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jbossas4 (Ubuntu)
Fix Released
Undecided
Sebastian Carneiro

Bug Description

During a rebuild test on precise with default-jdk switched to openjdk-7, a build failure was detected for jbossas4 version 4.2.3.GA-6.

See attached log for full build failure details.

This log snippet might also be of interest:

    [javac] ^
    [javac] /«PKGBUILDDIR»/ejb3x/src/main/javax/annotation/Resource.java:31: warning: unmappable character for encoding ASCII
    [javac] * resource in the bean???s environment. The name property refers to the name by
    [javac] ^
    [javac] /«PKGBUILDDIR»/ejb3x/src/main/javax/annotation/security/RunAs.java:35: warning: unmappable character for encoding ASCII
    [javac] * all methods of the enterprise bean???s business, home, component, web service
    [javac] ^
    [javac] /«PKGBUILDDIR»/ejb3x/src/main/javax/annotation/security/RunAs.java:35: warning: unmappable character for encoding ASCII
    [javac] * all methods of the enterprise bean???s business, home, component, web service
    [javac] ^
    [javac] /«PKGBUILDDIR»/ejb3x/src/main/javax/annotation/security/RunAs.java:35: warning: unmappable character for encoding ASCII
    [javac] * all methods of the enterprise bean???s business, home, component, web service
    [javac] ^
    [javac] 7 warnings
      [jar] Building jar: /«PKGBUILDDIR»/jboss-ejb3x.jar
    [mkdir] Created dir: /«PKGBUILDDIR»/jmx/classes
    [javac] /«PKGBUILDDIR»/debian/build.xml:80: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
    [javac] Compiling 602 source files to /«PKGBUILDDIR»/jmx/classes
    [javac] /«PKGBUILDDIR»/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java:169: error: unmappable character for encoding ASCII
    [javac] * See JVM spec ???4.2 and ???4.3 for detailed description of the internal class name format and grammar notation.
    [javac] ^
    [javac] /«PKGBUILDDIR»/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java:169: error: unmappable character for encoding ASCII
    [javac] * See JVM spec ???4.2 and ???4.3 for detailed description of the internal class name format and grammar notation.
    [javac] ^
    [javac] /«PKGBUILDDIR»/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java:169: error: unmappable character for encoding ASCII
    [javac] * See JVM spec ???4.2 and ???4.3 for detailed description of the internal class name format and grammar notation.
    [javac] ^
    [javac] /«PKGBUILDDIR»/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java:169: error: unmappable character for encoding ASCII
    [javac] * See JVM spec ???4.2 and ???4.3 for detailed description of the internal class name format and grammar notation.
    [javac] ^
    [javac] /«PKGBUILDDIR»/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java:169: error: unmappable character for encoding ASCII
    [javac] * See JVM spec ???4.2 and ???4.3 for detailed description of the internal class name format and grammar notation.
    [javac] ^
    [javac] /«PKGBUILDDIR»/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java:169: error: unmappable character for encoding ASCII
    [javac] * See JVM spec ???4.2 and ???4.3 for detailed description of the internal class name format and grammar notation.
    [javac] ^
    [javac] 6 errors

BUILD FAILED
/«PKGBUILDDIR»/debian/build.xml:80: Compile failed; see the compiler error output for details.

Total time: 6 seconds
make: *** [debian/stamp-ant-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
────────────────────────────────────────────────────────────────────────────────
Build finished at 20111110-2142

Finished
────────

E: Build failure (dpkg-buildpackage died)

Related branches

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 jbossas4 (Ubuntu):
status: New → In Progress
assignee: nobody → James Page (james-page)
Revision history for this message
James Page (james-page) wrote :

This packages also needs some API updates for the JDBC API in Java 7.

tags: added: api
James Page (james-page)
Changed in jbossas4 (Ubuntu):
status: In Progress → Confirmed
assignee: James Page (james-page) → nobody
Revision history for this message
Bruno Girin (brunogirin) wrote :

Considering JBoss AS is currently at version 7, what is the rationale for keeping v4 in the repos? And wouldn't it be easier to upgrade to a more recent version? Note that I am a noob in packaging to this question is probably very stupid.

Revision history for this message
James Page (james-page) wrote :

Reconfirmed in Ubuntu Quantal - adding ftbfs tag.

tags: added: ftbfs
Changed in jbossas4 (Ubuntu):
assignee: nobody → Sebastian Carneiro (scarneiro)
Revision history for this message
Michael Terry (mterry) wrote :

Uploaded to quantal, it's waiting for approval.

Revision history for this message
Colin Watson (cjwatson) wrote :

There were two similar uploads in the queue for this; I accepted one (which had a slightly better changes and a proper Maintainer change in debian/control) and rejected the other.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jbossas4 - 4.2.3.GA-7ubuntu1

---------------
jbossas4 (4.2.3.GA-7ubuntu1) quantal; urgency=low

  * Fix FTBFS by implementing jdbc and ejb3 resource annotation for Java7,
    and setting encoding on javac targets (LP: #888943):
    - debian/patches/jdbc-jdk7: added implementation of JDBC resource
      adapters for JDK7.
    - debian/patches/ejb3-jdk7: added lookup attribute to Resource
      annotation for JDK7.
    - debian/build.xml: set encoding on javac targets.
 -- Sebastian Carneiro <email address hidden> Fri, 21 Sep 2012 01:21:48 -0300

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