JemBuilder performance when your source and/or output files are on a network drive - even a fast gigabit NAS - is hugely slower, especially if the output folder is on a network. By "hugely" I mean over 10X slower! So a build which takes 10 seconds to a local drive will take over 100 seconds to a network drive. Having the source files on a network does not have such a dramatic impact. This is true only for aJile 4.X and is not true for the old 3.16.09 release.

So we have taken to building with our source files on a network, and building to a local temp folder. It's a huge time savings.

The new version JemBuilder will read older .ajp files and appear to use them but it isn't doing the right thing and you will wind up with all sorts of strange errors such as "invalid optimization". You must use the wizard to make a new 4.X-compatible Jembuilder project when you are attempting to use old 3.16.09 project files.

It's too bad the new JemBuilder doesn't issue an error, warning, or convert the old files for you.

You must use new 4.X configurations with the newer aJile tools. These configurations come with aJile releases obtained from Systronix. Don't try to mix old and new target configurations!

If you are using serial I/O (using javaxcomm) in your embedded Java program, JemBuilder needs to be configured to enable serial drivers such as the internal UARTs com1 and com2, available on JStamp, JStik, and SaJe, and the external UARTS available on JStik with the optional Quad Serial board.

On the top menu bar in Jembuilder, click on Project-> Drivers and then be sure that com1 or com2 or both appear in the "installed drivers" section.

This screen capture to the left shows internal UART com1 and also two additional external UARTs selected. Note that these particular UARTs are only available if you are using the Quad Serial board.