I am trying to run JIBS on a 64 bit Windows machine (I updated the build.xml from the repository and am no longer using launch4j). When I build the project on a 64 bit Windows machine it opens the frame but none of the internal panels or anything useful to running the program. When I take those same jars and run them in a 32 bit Windows environment they work just fine. When I build on a 32 bit Windows system the program runs fine on the same system but when the JARs are moved to the 64 bit Windows system I get the same problem as described above.
Have you experienced this same problem? Is there a way to make JIBS run on 64bit systems?
Thanks,
SAM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I build all the production versions of JIBS on the 64 bit version of Windows7 Professional, so should not be a problem.
Does the production jar file do the same when downloaded?
Are you running in a command prompt from which you can see errors?
Note that JIBS uses Java 7 features so you need to make sure you compile and run on Java 7. Although the problem you mention should not really be a Java 7.
I just tried a build with batch file below and found a problem on build.xml line 77 in that the target should be 1.7 not 1.6. Fixed and checked back in. Should have affected compile, not runtime.
I run in Eclipse and compile the jar/exe using batch file below.
@echo off
cls
echo Building JIBS with Ant
d:
cd \dev\workspace\JIBS
set BIN_HOME=d:\dev\bin
set ANT_CMD_LINE_ARGS=
set ANT_HOME=D:\dev\apache-ant-1.8.2
set JAVA_HOME=C:\java\jdk1.7.0_02
set LAUNCH4J_HOME=D:\dev\launch4j
set CLASSPATH=
set EXCLUDES=
:setupArgs
if %1a==a goto doneStart
set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% %1
shift
goto setupArgs
:doneStart
echo Calling ant with local build.xml…
call %ANT_HOME%\bin\ant.bat -buildfile build.xml %ANT_CMD_LINE_ARGS%
goto end
:end
echo Batch file exiting.
set ANT_CMD_LINE_ARGS=
Here is batch file I use to run JIBS in command window:
@echo off
cls
set JAVA_HOME="C:\Java\jdk1.7.0_02"
set CLASSPATH=D:/dev/workspace/deliver/JIBS.jar;
rem set CLASSPATH=D:/dev/workspace/deliver/JIBS.jar
echo CLASSPATH
%JAVA_HOME%\bin\java -version
rem %JAVA_HOME%\bin\java org.gerhardb.jibs.JibsJarStartup
%JAVA_HOME%\bin\java -Xms500M -Xmx1000M org.gerhardb.jibs.Jibs
@echo go.bat: I'm back!
Gerhard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-05-04
Thank you for your reply. I forgot that I asked this question. The JIBS ant builder works just fine. I'm not sure what I was doing wrong but things are working now. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to run JIBS on a 64 bit Windows machine (I updated the build.xml from the repository and am no longer using launch4j). When I build the project on a 64 bit Windows machine it opens the frame but none of the internal panels or anything useful to running the program. When I take those same jars and run them in a 32 bit Windows environment they work just fine. When I build on a 32 bit Windows system the program runs fine on the same system but when the JARs are moved to the 64 bit Windows system I get the same problem as described above.
Have you experienced this same problem? Is there a way to make JIBS run on 64bit systems?
Thanks,
SAM
I build all the production versions of JIBS on the 64 bit version of Windows7 Professional, so should not be a problem.
Does the production jar file do the same when downloaded?
Are you running in a command prompt from which you can see errors?
Note that JIBS uses Java 7 features so you need to make sure you compile and run on Java 7. Although the problem you mention should not really be a Java 7.
I just tried a build with batch file below and found a problem on build.xml line 77 in that the target should be 1.7 not 1.6. Fixed and checked back in. Should have affected compile, not runtime.
I run in Eclipse and compile the jar/exe using batch file below.
@echo off
cls
echo Building JIBS with Ant
d:
cd \dev\workspace\JIBS
set BIN_HOME=d:\dev\bin
set ANT_CMD_LINE_ARGS=
set ANT_HOME=D:\dev\apache-ant-1.8.2
set JAVA_HOME=C:\java\jdk1.7.0_02
set LAUNCH4J_HOME=D:\dev\launch4j
set CLASSPATH=
set EXCLUDES=
:setupArgs
if %1a==a goto doneStart
set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% %1
shift
goto setupArgs
:doneStart
echo Calling ant with local build.xml…
call %ANT_HOME%\bin\ant.bat -buildfile build.xml %ANT_CMD_LINE_ARGS%
goto end
:end
echo Batch file exiting.
set ANT_CMD_LINE_ARGS=
Here is batch file I use to run JIBS in command window:
@echo off
cls
set JAVA_HOME="C:\Java\jdk1.7.0_02"
set CLASSPATH=D:/dev/workspace/deliver/JIBS.jar;
rem set CLASSPATH=D:/dev/workspace/deliver/JIBS.jar
echo CLASSPATH
%JAVA_HOME%\bin\java -version
rem %JAVA_HOME%\bin\java org.gerhardb.jibs.JibsJarStartup
%JAVA_HOME%\bin\java -Xms500M -Xmx1000M org.gerhardb.jibs.Jibs
@echo go.bat: I'm back!
Gerhard
Thank you for your reply. I forgot that I asked this question. The JIBS ant builder works just fine. I'm not sure what I was doing wrong but things are working now. Thanks.