Maven Setup

Each of these setup processes can be done with user-wide authentication or project-local authentication. Although most modellers need user-wide authentication, there may be instances where a different license is necessary in one or more specific projects. The setup processes go through user-wide setup first, followed by project-local setup.

Maven Authentication

Maven will search for a file called settings.xml in its home directory when creating a default server authentication configuration.

Use the following commands to create and open the Maven home directory, .m2, if it hasn't been created already.

On Windows (WinKey + R, cmd):

md "%userprofile%\.m2"
explorer "%userprofile%\.m2"

On macOS and Linux:

mkdir -p ~/.m2
open ~/.m2      # macOS
xdg-open ~/.m2  # Linux

Next, if settings.xml doesn't exist in that directory, create it. The basic structure of the file should look like the following:

<?xml version="1.0" encoding="UTF-8"?>
<settings>
    <servers>
        <server>
            <id>simudyne.jfrog.io</id>
            <username></username>
            <password></password>
        </server>
    </servers>
</settings>

Place your username and password in the appropriate XML elements, then save the file. The username and password are located in your Maven access token file.

The format of the Maven access token file has changed slightly over time. For older Simudyne users, the username is the name of the access token file, and the password is the file content. Newer users can find both the username and password in the contents of the access token file, as the first and second line respectively.

Proxy Configuration

Your organisation may require you to use a proxy for your Maven requests. The proxy settings will need to be added to the settings.xml file under the proxies header. For more information on configuring a proxy, see the Maven proxy configuration guide.

There are two different ways Maven can be configured for project-local authentication:

1. On the command line, pass -S settings.xml to any mvn command.
2. In the IDE, override the Maven configuration on a per-project basis. For IntelliJ IDEA (Simudyne's recommended IDE):
   • Go to Build, Execution, Deployment → Build Tools → Maven.
   • Tick the override box for User settings file.
   • Set it to point to the settings.xml file in your project.

---

Simudyne License

SDK users should receive a Simudyne license file as part of the onboarding process. Please contact support@simudyne.com if there are any license problems.

There are several ways that Simudyne licenses can be configured:

1. Copy the license to the project's root directory and rename it to licenseKey. The SDK will then prioritise this license.
2. Add a core.license-file property to the simudyneSDK.properties file. The value should be the path to your license relative to your project root directory.
3. Pass the license location via the Java command line using the -DsimudyneLicenseFile flag.