Welcome to the MacNN Forums.

depolitic · Dec 27, 2003, 05:38 AM

Hi - I need to get JBuilder X running on my Panther Laptop. Has anyone had any success getting it to run.

I found instruction for JBuilder9 but I cannot get it to work.

I have downloaded the Linux JBuilderX and am running 10.3.2

Any help would be most welcome.

MacGallant · Jan 14, 2004, 07:07 PM

Originally posted by depolitic:
Hi - I need to get JBuilder X running on my Panther Laptop. Has anyone had any success getting it to run.

I found instruction for JBuilder9 but I cannot get it to work.

I have downloaded the Linux JBuilderX and am running 10.3.2

Any help would be most welcome.

Like you, I would like to get JBuilder X to work on my mac too.
I downed the faq sheet for the system requirements for JBuilder x. For JBuilder X Foundation, it stated the following for the Mac: it is available on CD or as a separte download. OSX 10.2 is required, which is fine with me. But I checked their download site and there isn't a link for Mac OS X! I then emailed Borland and they told me to buy the Developer Edition, which I believe is $500! I'm a poor college student for crying out loud!

The fact that Borland fails to acknowledge the Mac in this way is a slap in the face to the Mac community! Esp. student programmers!

depolitic · Jan 15, 2004, 02:52 AM

I have made contact with borland support and am waiting for feedback.

I have also gone to Intellij.com and downloaded their IDEA ide, as it has gotten rave reviews. Also Intellij has the seance to support Mac os x fully and having used Intellij I must say that I am very impressed.

Have a look at Intellij and take your business else-were if Borland does not want it.

MacGallant · Jan 16, 2004, 03:21 PM

Good news! I just spoke with customer support and they said that the Mac OSX version of JBuilder X Foundation will be up on their site and released by the end of January!

depolitic · Jan 16, 2004, 06:23 PM

Thanks very much forr the information. I was still waiting for them to contact me. Lets see what comes of it.

hengx · 06:01 PM

I got it to work. Just follow the same guidelines for using the linux version of JBuilder 9 on OS X.

Download the linux version of JBuilder Foundation X. Unpack it to Desktop and open the Terminal.

hengx@Logaritmen: ~ $ cd ~/Desktop/jbx_linux

hengx@Logaritmen: ~/Desktop/jbx_linux $ sh ./fnd_install.bin LAX_VM /usr/bin/java

Do not change the folder, where JBuilder insists to install itself, it will cause the app to hang.

After it has installed itself in either /Developer/Applications/ or in /Applications, depending on if you have Apple Developer Tools installed, you have to place the following script in JBuilder/JBuilder.framework/bin. Call it something like JBuilderX.command - Do not use an editor that uses invisible control characters like Word or something like that. I think TextEdit should be ok.

Code:
#!/bin/sh
#
# Just a quick script to launch jbuilder on a unixy platform.
# 
#
# dave@minnigerode.org
# 
# (based on a script from Paul Furbacher @ borland.public.jbuilder.macintosh@ne...ps.borland.com)
#

#Set the name of the app - no spaces
APPNAME="JBuilderX"

# The main client class
MAIN="com.borland.jbuilder.JBuilder"

# Where we're called from
INITIALDIR=$PWD

# Where the script is at
RUNIN=`dirname $0`

# go to the script location
cd $RUNIN

# where the libs are
LIBDIR="../lib";

# where the patchs are
PATCHDIR="../patch"


# The boot classpath
BOOTCLASSPATH="$LIBDIR/lawt.jar:$LIBDIR/TabbedPaneFix.jar:$LIBDIR/SequencedEventFix.jar:$LIBDIR/javac.jar:$LIBDIR/JarManifestFix.jar"

if [ `uname` = "Darwin" ]; then 
    BOOTCLASSPATH="$BOOTCLASSPATH:/System/Library/Java/Extensions/MRJToolkit.jar"
fi

# add the arg flag for bootclasspath
BOOTCLASSPATH="-Xbootclasspath/p:$BOOTCLASSPATH"


# get a list of all the jars - use find since it does the paths nicely
JARS=`find $LIBDIR -name *.jar`

# also get a list of all the ext jars if they exsist. Ok to get dupes of above.
# we just want to make sure these are on the classpath first (see below).
if [ -x $LIBDIR/ext ]; then
    EXTJARS=`find $LIBDIR/ext -name *.jar`
fi



# create the classpath with the ext jars first and then the libs.
CP=.
if [ -x $LIBDIR/ext ]; then
    for X in $EXTJARS; do
        CP=$CP:$X
    done
fi
for X in $JARS; do
     CP=$CP:$X
done

# any patches?
if [ -x $PATCHDIR ]; then
   PATCHJARS=`find $PATCHDIR -name *.jar`
   for X in $PATCHJARS; do
      CP=$X:$CP
   done;
fi


# on OS X we need to set some more defines and -X stuff
# TODO: Need to check this against the current JVM and add/del stuff
case `uname` in
    "Darwin")
            DEFS=$DEFS" -Dcom.apple.mrj.application.apple.menu.about.name=$APPNAME"
            DEFS=$DEFS" -Dapple.laf.useScreenMenuBar=true"
            DEFS=$DEFS" -Dapple.awt.brushMetalLook=false"
            DEFS=$DEFS" -Dcom.apple.hwaccel=true"
            DEFS=$DEFS" -Xdock:name=$APPNAME"
            DEFS=$DEFS" -Xverify:none"
            DEFS=$DEFS" -Xmaxf0.2"
            DEFS=$DEFS" -Xminf0.2"
            DEFS=$DEFS" -Xms32m"
            DEFS=$DEFS" -Xmx256m"
            ;;
    *)
            DEFS=$DEFS" -Xverify:none"
            DEFS=$DEFS" -Xmaxf0.2"
            DEFS=$DEFS" -Xminf0.2"
            DEFS=$DEFS" -Xms32m"
            DEFS=$DEFS" -Xmx256m"
            echo "Need to add the defs for your platform!"
            ;;
esac


# echo what were going to do
echo "Will run jbuilder with: java  $BOOTCLASSPATH $DEFS -cp $CP $MAIN"

# finally run the app
java  $BOOTCLASSPATH $DEFS -cp $CP $MAIN $@


# and cd back to where we came from when the app exits
cd $INITIALDIR

You can now just create an Alias to JBuilderX.command and call it something like JBuilder and put in the dock.

depolitic · 04:00 PM

Thanks all so much, however your commands did not work and files you mention are not part of the English Linux jbuilderx that I have.

Here is what I used.

1- Extract jbuilderx_linux.tar.gz to your desktop.

2- cd ~/Desktop/Linux/Linux

3- sh ./ent_install.bin LAX_VM /usr/bin/java

Now it finds the correct files and runs fine.

Maybe we have different versions.

Also their is no need to for the script, because their is an JBuilder.app in the JBuilder folder. I do not understand this. Why did Borland say that a Mac OS X version will only be available later. When the Linux version has inside it a full Mac version, and all they had to do was give us the instructions for the install.

What going on????? Is this discriminations, did Borland decide to with hold the Mac version to prove yet again that apps on a Mac always come later then on Windows. Or did I inadvertently download the Mac version that was not public available and just haven to be called jbuilderx_linux.tar.gz. So what up.

Because my jbuilderx_linux.tar.gz produced a full Aqua JBuilder with correctly menu bar placement, full 128 dpi icons. Please explain.

hengx · 06:02 PM

3- sh ./ent_install.bin LAX_VM /usr/bin/java

ent_install.bin, isn't that the enterprise version?

The .app files in the foundation version do not work, don't know why they are included. Probably for future work...

The version I use also has Aqua menus, that's because it uses the systems layout manager, I think.

Try to download the Foundation version and create the .command file

MacGallant · Jan 23, 2004, 09:10 PM

Thanks hengx, but here's how i got it to work(I'm using JBuilderXFoundation
in terminal, i used tcsh
step 1. type "cd " and drag the jbuilder linux folder on the terminal and press enter key
step 2. type "sh ./fnd_install.bin LAX_VM /usr/bin/java" and press enter
step 3. follow the rest of hengx's instructions
step 4. save the script in textedit(in prefs select text not rtf) and name it"JBuilderX.command" and put it in "JBuilder/JBuilder.framework/bin"
step 5. in terminal type"chmod +x JBuilderX.command" this will make the script an executable
step 6. make an alias of JbuilderX.command and click it to launch

Originally posted by hengx:
I got it to work. Just follow the same guidelines for using the linux version of JBuilder 9 on OS X.

Download the linux version of JBuilder Foundation X. Unpack it to Desktop and open the Terminal.

hengx@Logaritmen: ~ $ cd ~/Desktop/jbx_linux

hengx@Logaritmen: ~/Desktop/jbx_linux $ sh ./fnd_install.bin LAX_VM /usr/bin/java

Do not change the folder, where JBuilder insists to install itself, it will cause the app to hang.

After it has installed itself in either /Developer/Applications/ or in /Applications, depending on if you have Apple Developer Tools installed, you have to place the following script in JBuilder/JBuilder.framework/bin. Call it something like JBuilderX.command - Do not use an editor that uses invisible control characters like Word or something like that. I think TextEdit should be ok.

Code:
#!/bin/sh # # Just a quick script to launch jbuilder on a unixy platform. # # # dave@minnigerode.org # # (based on a script from Paul Furbacher @ borland.public.jbuilder.macintosh@ne...ps.borland.com) # #Set the name of the app - no spaces APPNAME="JBuilderX" # The main client class MAIN="com.borland.jbuilder.JBuilder" # Where we're called from INITIALDIR=$PWD # Where the script is at RUNIN=`dirname $0` # go to the script location cd $RUNIN # where the libs are LIBDIR="../lib"; # where the patchs are PATCHDIR="../patch" # The boot classpath BOOTCLASSPATH="$LIBDIR/lawt.jar:$LIBDIR/TabbedPaneFix.jar:$LIBDIR/SequencedEventFix.jar:$LIBDIR/javac.jar:$LIBDIR/JarManifestFix.jar" if [ `uname` = "Darwin" ]; then BOOTCLASSPATH="$BOOTCLASSPATH:/System/Library/Java/Extensions/MRJToolkit.jar" fi # add the arg flag for bootclasspath BOOTCLASSPATH="-Xbootclasspath/p:$BOOTCLASSPATH" # get a list of all the jars - use find since it does the paths nicely JARS=`find $LIBDIR -name *.jar` # also get a list of all the ext jars if they exsist. Ok to get dupes of above. # we just want to make sure these are on the classpath first (see below). if [ -x $LIBDIR/ext ]; then EXTJARS=`find $LIBDIR/ext -name *.jar` fi # create the classpath with the ext jars first and then the libs. CP=. if [ -x $LIBDIR/ext ]; then for X in $EXTJARS; do CP=$CP:$X done fi for X in $JARS; do CP=$CP:$X done # any patches? if [ -x $PATCHDIR ]; then PATCHJARS=`find $PATCHDIR -name *.jar` for X in $PATCHJARS; do CP=$X:$CP done; fi # on OS X we need to set some more defines and -X stuff # TODO: Need to check this against the current JVM and add/del stuff case `uname` in "Darwin") DEFS=$DEFS" -Dcom.apple.mrj.application.apple.menu.about.name=$APPNAME" DEFS=$DEFS" -Dapple.laf.useScreenMenuBar=true" DEFS=$DEFS" -Dapple.awt.brushMetalLook=false" DEFS=$DEFS" -Dcom.apple.hwaccel=true" DEFS=$DEFS" -Xdock:name=$APPNAME" DEFS=$DEFS" -Xverify:none" DEFS=$DEFS" -Xmaxf0.2" DEFS=$DEFS" -Xminf0.2" DEFS=$DEFS" -Xms32m" DEFS=$DEFS" -Xmx256m" ;; *) DEFS=$DEFS" -Xverify:none" DEFS=$DEFS" -Xmaxf0.2" DEFS=$DEFS" -Xminf0.2" DEFS=$DEFS" -Xms32m" DEFS=$DEFS" -Xmx256m" echo "Need to add the defs for your platform!" ;; esac # echo what were going to do echo "Will run jbuilder with: java $BOOTCLASSPATH $DEFS -cp $CP $MAIN" # finally run the app java $BOOTCLASSPATH $DEFS -cp $CP $MAIN $@ # and cd back to where we came from when the app exits cd $INITIALDIR

You can now just create an Alias to JBuilderX.command and call it something like JBuilder and put in the dock.

hengx · Jan 24, 2004, 10:57 AM

Originally posted by MacGallant:
...
step 5. in terminal type"chmod +x JBuilderX.command" this will make the script an executable
...

Hi MacGallant, forgot that one. That's an important point :-)