Getting Started : Development Environment
To develop on Atoti, you should have a computer with several cores, running either Linux or Windows 7+ 64-Bit.
The current version of Atoti Server is based on Java 21.
The path to your JDK root directory should be registered in the JAVA_HOME environment variable.
You can check your installation by running java -version in a new shell.
The project build is based on Maven.
The path to your maven installation directory should be registered in the M2_HOME environment variable.
You can check your installation by running mvn -v in a new shell.
You can use your favorite IDE. If you don't have one, you can try IntelliJ.
A license file is required to activate any Atoti installation
To register your license check the License page.
If you haven't done it yet, download the Atoti maven repository and the sandbox.
To make sure all dependencies are correctly installed, we recommend running mvn clean install -DskipTests
on the sandboxes directory prior to importing it as a maven project in your IDE.
Many classes visible from Atoti jars are considered internal classes.
These internal classes are located in packages containing internal or private_.
Examples:
com.activeviam.database.sql.internal.schema.ISqlFieldDescription, indicated by the "...sql.internal.schema..."com.activeviam.database.bigquery.private_.BigqueryDataVersion, indicated by the "...bigquery.private_..."
These classes can be changed at any point in time, without regard for backward compatibility, without warning, without mention in the changelog, and without migration notes.
Users must not use them. This will never be an issue as they are never exposed to users. The APIs always return their interfaces or wrap them. They are only visible through debuggers.