Bugs item #1064328, was opened at 2004-11-11 07:39 Message generated for change (Comment added) made by andd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1064328&group_id=22866
Category: Build System Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Ulrich Romahn (diggermaus) Assigned to: Nobody/Anonymous (nobody) Summary: JBoss 3.2.6 cannot be build using IBM SDK 1.4.2 Initial Comment: Whe trying to build JBoss 3.2.6 using IBM's JDK1.4.2-1.0 on a Linux box, I get the following exception during the compile of JBoss JMX: error: IO exception sun.io.MalformedInputException I get this error exactly three times but no further message nor a stack trace. I assume that there are some dependencies to Sun's SDK in the build system (Ant) because of the sun.io exception which I should't see using IBM's JDK. Howver, the precompiled version (with Sun's JDK, I assume) seems to run flawlessly on IBM's JDK. I would really like to build JBoss with IBM's JDK because IBM's javac produces much more optimized code and performs much faster on Linux with the 2.6 kernel. ---------------------------------------------------------------------- >Comment By: Dimitris Andreadis (andd) Date: 2004-11-12 09:10 Message: Logged In: YES user_id=583305 Cleaning and posting back those files would be great, since we rarely use IBM's JDK here! Thanks ---------------------------------------------------------------------- Comment By: Ulrich Romahn (diggermaus) Date: 2004-11-12 04:01 Message: Logged In: YES user_id=579922 Thanks to the comment below, I got past the first error, but now IBM's javac reports another compile error: In class org.apache.axis.components.net.SunJSSESocketFactory.java it references classes from Sun that obviously cannot be resolved. It references classes in the package com.sun.net.ssl which are not part of IBM's JDK. I assume that JBoss has never really been compiled with the IBM JDK because otherwise this would have been caught. I am not sure if anybody at JBoss will tackle this issue or if it will be my responsibility to "clean" these references and then feed it back to JBoss. ---------------------------------------------------------------------- Comment By: Ulrich Romahn (diggermaus) Date: 2004-11-12 04:00 Message: Logged In: YES user_id=579922 Thanks to the comment below, I got past the first error, but now IBM's javac reports another compile error: In class org.apache.axis.components.net.SunJSSESocketFactory.java it references classes from Sun that obviously cannot be resolved. It references classes in the package com.sun.net.ssl which are not part of IBM's JDK. I assume that JBoss has never really been compiled with the IBM JDK because otherwise this would have been caught. I am not sure if anybody at JBoss will tackle this issue or if it will be my responsibility to "clean" these references and then feed it back to JBoss. ---------------------------------------------------------------------- Comment By: Igor Fedorenko (igorfie) Date: 2004-11-11 08:20 Message: Logged In: YES user_id=232950 As a guess, try "export LANG=en_US" before running the build. I had similar problem building other software on redhat 9 box. It turned out that sources had non-ascii characters in comments. IBM I/O libs correctly rejected to read them using default UTF-8 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1064328&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
