Software Setup

Forewords

Unless stated otherwise, all directories mentioned in this documentation are relative to the directory where you placed the Framework files on your file system. To simplify instructions, this directory will be referred to as $FRAMEWORK_DIR in the following sections. Please make sure to replace $FRAMEWORK_DIR in the following sections with the actual path on your file system.

Install MicroEJ SDK 6

The installation of MicroEJ SDK 6 is required before proceeding with the following steps.

Please refer to the installation chapter of the SDK 6 User Guide before continuing.

If you are already using MicroEJ SDK, make sure you are using the latest version. To check for updates, open your IDE settings and look for MicroEJ in the installed plugins.

Accept SDK EULA

The use of MICROEJ SDK 6 requires to accept the SDK EULA.

Please refer to the official documentation for the SDK EULA acceptation.

Configure the Repositories

During the installation of MicroEJ SDK 6, Gradle has been configured to fetch dependencies from the MicroEJ online repositories (Central and Developer).

However, VEE Wear relies on dependencies that are not available in these online repositories. Therefore, the Gradle configuration must be modified to also resolve dependencies from the Offline Repository provided with the framework.

Follow the steps below to complete the setup:

1. Open the Gradle configuration file $USER_HOME/.gradle/init.d/microej.init.gradle.kts,

2. Edit the configuration to add the Offline Repository to the list of known repositories:

   allprojects {
           repositories {
                   /* Local Repository */
                   maven {
                           name = "localRepository"
                           url = uri("${userHome}/.microej/repository")
                   }
                   /* VEE Wear Offline Repository */
                   ivy {
                           name = "wearRepository"
                           url = uri("$FRAMEWORK_DIR/repository")
                           patternLayout {
                                   artifact("[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier])(.[ext])")
                                   ivy("[organisation]/[module]/[revision]/ivy-[revision].xml")
                                   setM2compatible(true)
                           }
                   }
   
                   // Other repositories omitted for brevity
           }
   }
   

   Note

   Make sure to place the VEE Wear Offline Repository in second position in the list, after the localRepository. This ensures that it takes precedence over online repositories when resolving dependencies.

For more information about how to use Offline Repositories, please refer to our official documentation.

Open the Projects

The provided projects are interdependent, meaning they rely on each other for successful compilation and execution.

The dependencies are as follows:

• The VEE Port ats3085s-veeport depends on the Mock wear-mock

• The Kernel wear-kernel depends on the VEE Port ats3085s-veeport

• The Applications in wear-samples depend on the Kernel wear-kernel

• The Application wear-facer-app depends on the Kernel wear-kernel

When working with interdependent projects, one option is to use Gradle’s includeBuild feature to reference the projects, as it is done in this Developer Package. Gradle will resolve the dependencies from the included build’s source instead of fetching them from an external repository. This allows for local development and testing of dependencies without needing to publish them first.

After loading the Facer application or the samples with your IDE, all the other necessary projects will be visible.