I use Cubic. Works fine for me. Some inital configuration is necessary, but once it's done, I found I like it.

Remember I got a note with it that aided the installation process. You should copy the CD contents to yoiur harddrive: http://amigaworld.net/modules/newbb/v ... p?topic_id=28289&forum=32.

Have tried CodeBench on occasions, but the inital setup for compiling a simle project has always bored me. I don't understand the need to manually add all files individually, and having a separate header directory. What I'd really like to do is just to open a file, and by a key press make an existing makefile. Although I absolutely love the effort, and all the nifty features with SVN and community-thingie.

So, if you're beginning a new project, I'd consider CodeBench.

@Raziel
Thanks for trying it out!
I've come a bit longer; it looks as though the client is downloading stuff, but I get no files. I really have to try it more on my Mac (or Linux with jamvm and GNU Classpath), just so I'm not trying anything that isn't supposed to not work.

Like so wisely suggested, I contacted Dietmar (the author). He replied quickly and I now got it working. I can now compile Java programs in Cubic without much problem (although rather much waiting)! I'll try and release some info/example on it some time soonish.

Peter Werno has kindly redirected the "old" address to the JAmiga blog. So if you want to reach the blog, you can simply type www.jamiga.org in your browser.

The jamiga2.blogspot.com address will still work though.

On www.jamiga.org (sic!) you can find an archive with the Eclipse JGIT client. I don't know how it works exactly, but I've managed to create some directories with it and seeminlgy started to download stuff.

But I'm rellay not a GIT user, so I have no good knowledge of GIT trees and repos. So if anyone with some GIT knowledge could try this out, I'd be very grateful!
The GIT client can be downloaded from the blog.

The client requires the new native library available in AmiUpdate.

Does anyone know how you can utilize the console.api in Cubic IDE?

I've looked at the Hollywood-plugin and the SDK plugin, and they both use the console.api. When looking in f.i. Customize/Settings, Pool, Plug-ins/c++.api, Console/Plug-Ins and the console.api, there are various arguments used. I tried changing some and deduct from the console.api binary what other arguments might be possible. Sometimes I get errors complaining about the arguments and sometimes not.
I'm thinking that the PIPECON device is used somehow, but don't know if it's possible to utilize it without creating your own .api binary (both Hollywod and the SDK building uses their own .api binary). I have tried to just redirect some echos to PIPECON in varuious ways (usign teh same name as stated in the argument) but without any result.

What I'd liked to do is to just run any arbitrary command, and get its output in the console window in the Cubic screen.

@ddni
Some applications when downloaded from os4depot might also, in lack of install script, only require you to copy all files to where-ever you want, and run the program in order to be updateable by AmiUpdate.

Whenever you run a program in AmigaOS 4, an entry is created in the AppDir: entry. This entry is used by some AmiUpdateable programs in order to find where it is located, and check its version.

So, I'd suggest to not manually run the Autoinstall script, nor using it as guide, unless the program's manual tells you to. If not manual or install script is found, I do suggest to contact the developer.

@JosDuchIt

Great that you got it working! I think it all comes from my installer not coping with spaces. After your first install I can only assume that some AmiUpdated stuff wasn't copied correctly.

Once again, thank you for testing!

That error could be due to a missing jar-file in JAmiga:lib. It should've been installed with the developer's kit, but perhaps it's disappeared between your installs?

Anyhow, do a:

If everything is ok, you should hava a JAR-file, ecj-4.3.jar there.

If you don't, then that's what's wrong.

Then, in order to download the dev-kit again, you need to do:


If you run AmiUpdate now, you should have the JAmiga developers kit in the list again. And hopefully when you install it again, everything should work.

(If the AmiUpdate for some reason fails, it's most likely due to some file being locked by the JamVM process (yet another bug!). Please copy the "unpacked" dir in ram: to disk, reboot, and copy the "unpacked/JAmiga"-directory content to JAmiga:. Then, perhaps, if all the stars are aligned, it'll work.)

That's what I can come up with at the moment. Once again, thanks for your patience!

@JosDuchIt
Oh no...
But, you're at lot closer now, the text "JAmiga has been successfully installed!" Is the JVM actually running a Java application. So that's one step closer.

Could you paste the output of the compile after this new install?

@ddni
Well, to be honest, for an end user there might not be an awful lot to do with JAmiga currently.

I'm putting some hope into other Java developers in Amiga land to create some useful console applications (which could be controlled using ARexx for instance). I have my Twitter console client, which mostly serves as a proof-of-concept, and example of what can be done. I'm touching up some details there and plan to release it soonish, together with some more developer documentation.

But for now, end-user with no intention at developing stuff might as well stayaway from JAmiga. But I'm working on getting something useful to do.

@jaokim
Okay, so, I apparently can't do anything right. Now I missed the quotes surrounding disk name in the user-startup file.

That means JAmiga will work when freshly installed, but not when rebooted (if you have spaces in your drive name).

Either wait for new os4depot archive and install again (sigh!), or simply edit your s:user-startup.
If you have spaces in the JAmiga path, please add double quotes on your path, from something like:


to:



New archive in os4depot upload queue...

It has been reported by JosDuchIt that installing JAmiga 1.2 to a drive (or drawer) with a space in the name, failed when unpacking vital classes.

This has now been fixed.

You can download the updated archive from os4depot.

This bug exists in JAmiga 1.2 archive downloaded from os4depot on or before the 5:th of january 2014, having Install script version 1.2.

Sorry for the inconvenience.

Please report any irregularities (or why not, success stories) here on amigans.net.

Edited: Entire archive is now uploaded and approved on os4depot.

I've now fixed the install script: you can download the script from here, and replace the old install-file from the os4depot archive with this new one (v 1.3). You can simply unpack it to the same directory.
I'll upload a new archive to os4depot soon.

Once again, thank you for testing, and sorry for the inconvenience!

@JosDuchIt

Hmpf. It seems my installation script doesn't work very well for partitions with space in the name.

If you don't want to wait for me to fix the installation script, I *think* you could extract the two archives manually:
Extract classes.lha to "JAmiga:jvm/share/jamvm/classes"
Extract classpath.lha directly to "JAmiga:"

Or you can wait for me to fix the install script -- I'll put up the script as a single download, as well as replacing the os4depot archive.

The reason you got an error trying to extract classes.lha to JAmiga: directly, is that it has a drawer named "jamvm", which clashes with the binary file "jamvm".

Thank you for reporting your issue, being patient and trying different things! I guess other's must have had your problems as well!

Well that's just plain wrong.

Can you remember if anything went wrong with the install? The installation should automatically run UnArc (SYS:Utilities/unarc) twice to perform the unpacking of all the classes (a lot of .class files). Have you made any changes that might affect UnArc?
When did your first install JAmiga? Can you remeber if it was from the full 1.1 or 1.2 archive, or perhaps even before that?

Either way, I think your best choice is to install JAmiga again, using the os4depot archive, and then AmiUpdate it.
No one else has reported similar issues, so it might be better to start fresh.

@TSK:

Ah. I was worried I'd be in for a complicated bug hunt... :) Good that it works!

I'm still figuring out the best way to use AmiUpdate for all these tiny updates here and there, hope I've got it sorted now. Soonish I'll be releasing my tiny Twitter application along with some more developer documentation.

@JosDuchIt
Quote:

The CLASSPATH is strange; there a comma missing between the assigns, and the JAmiga assign should't need to be there.

Please do this:
<code>
delete ENV:CLASSPATH
delete ENVARC:CLASSPATH

setenv SAVE CLASSPATH CURRDIR:,
</code>

The JAmiga:JAmiga should then hopefully say "JAmiga has been successfully installed!" in the end

You can see current snapshot of what JAmiga:JAmiga should say here: https://code.google.com/p/jamiga2/wiki/CurrentVersion (your's do however look mostly correct.)

<i>If it still doesn't work</i>, could you please verify that you have a file named <b>VMClassLoaderData.class</b> in JAmiga:jvm/share/jamvm/classes/<b>jamvm/java/lang/</b>.

That's basically what this says you don't have:
Quote:

@TSK:

That's really strange. I just did the same on my debug system -- installed 1.2 from os4depot, and I found 5 JAmiga updates available in AmiUpdate. I've put a screengrab of it at os4depot. (It hasn't been approved at time of writing this though.)

Do you have more than one installations of JAmiga? Does the assign point to the correct drawer? Is it a fresh reboot? (I'm thinking if the libraries are somehow cached.)

@spotUP

Yes, only console based stuff currently. I've tried finding existing console applications, but I think we're better of build our own. I had my infamous Twitter example, which merely shows an example of using third party, unmodified JAR files. Its not terribly exiting, but with some clever Arexx-ing I think the use of third-party libraries might be useful. One could theoretically use some sort of Java Google calendar library and synn stuff with limpidclock, for instance. But that requires some amount of Java programming knowledge - but it isn't that hard.

I'm currently looking at enabling a GIT versioning client, but that requires another native library which I haven't finished yet (as described on the blog).

The crash would be interesting seeing!