Pitfalls for Greta development

Add dependent module as a java project, not .jar file

You should add dependent module as a java project as long as possible. This controls compilation order.

Right-click on a module in Projects pane in Netbeans, and select properties.

In Libraries category, select "Add Project", not "Add Library" or "Add JAR/Folder".

Only for external JAR packages which you cannot edit inside of the libraries, you can add by "Add JAR/Folder" or "Add Library".

Do not select "Compile on Save"

How to find this function:

1. right-click on a module in Projects pane in Netbeans, and select properties
2. in Libraries category, select "Add Project", not "Add Library" or "Add JAR/Folder"

Since I observed that unstable behaviors of this function, I personaly recommend not to enable this function.

But please note that, by disabling this function, you need to wait longer when you launch "Modular.jar" application.

When you really want to decrease the compilation time, you can enable "Compile on Save" and "Track Java Dependencies" together. You need to change them for all the modules. If you mix two of them, Greta will be very unstable.

Check TCP/IP port conflict

Some libraries use TCP/IP communication within/between components.

Before you establish new TCP/IP communications, you should check Communication-port-list

Do not use "Clean and build"

It seems there is a bug in "Clean and build", I recommend to use "Clean" and "Build" separately when you compile projects.

When I use "Clean and build", I faced compile errors when there are dependent libraries which are added not recommended way (check here for the recommended way to add dependent modules).

When you create a new module, do not forget to change dist path

You must change dist path to have appropriate relative locations to other modules in the Greta system.

Please check here for the detail.

Known issues

• There are many low documented modules