That message would seem to be complaining about a classpath issue. Recall that Java files must be in folders that reflect the package name.

I'm not up to date on the implications of Rosetta with regard to native code that was compiled for PowerPC. If your native code was compiled for Intel, then Rosetta should not be involved.

Before getting into projects that use native code, you should test some pure Java projects to make sure you have everything set up correctly.
And of course, it would be best to avoid native code entirely unless you can't help it.

Two years ago, I managed to get JBuilderX up using the following steps and it might help:

OS: Mac OS X 10.3.2 with Java 1.4.2 update

Steps:

- It presumes that you have registered with Borland website and installed the Developers' Tools for Panther. Go to http://www.borland.com/products/down..._jbuilder.html to download "jbx_linux.tar" from the list named "Foundation" for a free full English version of JBuilderX installation file.

- An actvation file "Reg426.txt" will be sent to your email account. Save this file under /Users/username directory.

- Untar the downloaded "jbx_linux.tar" file and you should have a folder "jbx_linux".

- Create a "JBuilderX" directory under /Developer/Applications.

- copy the contents of the folder "jbx_linux" to /Developer/Applications/JBuilderX.

- Using Terminal mode, type "which java" to search for the absolute path for java program. For my system, I got "/usr/bin/java". Go to the directory /Developer/Applications/JBuilderX and type "fnd_install.bin LAX_VM /usr/bin/java" to activate the installation.

- Next, refer to paragraph 4 at http://minnigerode.org/CA-SF/dave/jbuilder-mac.html
to download the activation file "run-jbuilder.command". Before making the file executable using "chmod x+run", use an editor to change the APPNAME from "JBuilder9" to "JBuilderX" in the command file.

- Just activate "run-jbuilder.command", JBuilderX should be activated. Drag the file "run-jbuilder.command" to the Dock for future activation.