Forge
How-to guides

Bootstrap the repositories

Create and populate the five repositories Forge resolves from, once per organisation.

Do this once per organisation, before anyone builds a resource. Forge resolves dependencies and generates descriptor metadata from a Maven repository, so an empty repository means neither works.

Skip this page entirely if your repositories already exist. Skip it too if you host artifacts locally rather than on a server.

1. Create the repositories

Create five repositories in Nexus or Artifactory. The names may differ, as long as the URLs you configure later match.

NameHoldsProperty
maven-gradle-plugin-snapshotsForge plugin snapshotssettings.gradle.kts
maven-gradle-plugin-releasesForge plugin releasessettings.gradle.kts
raw-catia-magic-assetsJDK, JRE, tool archives, user presets, AI-docs digestsassets.repository
maven-catia-magic-snapshotsResource and plugin snapshots, from Dassault and your own teamsnapshots.repository
maven-catia-magic-releasesResource and plugin releases, from Dassault and your own teamreleases.repository

The first two are found by the pluginManagement block in settings.gradle.kts, because Gradle resolves the plugin before it reads any property. The other three come from com.mbseconsulting.forge.* properties; see Properties. Forge skips any repository whose property is absent rather than failing, so an omission surfaces later as an unresolvable dependency instead of a clear error.

A project using profile bindings also depends on Anvil, published as two artifacts, a resource and a plugin: declare both on the catiaMagic configuration and install both with installCatiaMagicDependencies, exactly as Declare dependencies describes for any resource or plugin. Both resolve from maven-catia-magic-snapshots or maven-catia-magic-releases.

2. Download CATIA Magic from Dassault

Go to https://software.3ds.com/ and download the no-install archive for your tool, such as Cameo_Systems_Modeler_2026x_Refresh1_no_install.zip. Dassault documents which archive to take in Downloading installation files.

3. Build a user preset

A user preset carries the license-server configuration, so developers do not each configure it by hand.

  1. Extract the no-install archive.

  2. Launch it and choose Use default.

  3. Select Floating License, then FlexNet/DSLS and point the license server at your organization's server.

  4. Check out a license, ticking Automatically login each time … starts.

  5. Choose Don't share analytics.

  6. Close the tool and open its user-configuration folder:

    OSPath
    WindowsC:\Users\<you>\AppData\Local\<.tool-name>\<major-version>
    macOS, Linux~/<.tool-name>/<major-version>

    <.tool-name> is a hidden folder named after the product you installed — .cameo.systems.modeler, .magic.cyber.systems.engineer, .magic.systems.of.systems.architect. <major-version> is the major version only, so a 2026x Refresh1 install uses 2026x.

  7. Zip the folder's entire contents, naming the archive after the tool archive plus .user.zip e.g. Cameo_Systems_Modeler_2026x_Refresh1_no_install.user.zip.

The shared name is what pairs the preset with its archive, so the suffix matters.

4. Collect the JDK and JRE builds

Download the JDK and JRE that each CATIA Magic version needs, for every operating system your team develops on. The JDK matrix lists the versions and direct links.

5. Arrange the raw assets

Put everything in the folder structure the environment tasks expect — four folders, each holding its files directly. The asset layout gives the full structure and the two folders that appear later for AI-docs.

6. Configure the project

Create a project from magic-forge-template and point it at the repositories you just created. The template ships the URLs already, so this is an edit:

com.mbseconsulting.forge.assets.repository=https://your.company.com/repository/raw-catia-magic-assets
com.mbseconsulting.forge.releases.repository=https://your.company.com/repository/maven-catia-magic-releases
com.mbseconsulting.forge.snapshots.repository=https://your.company.com/repository/maven-catia-magic-snapshots

The template's settings.gradle.kts carries the pluginManagement block that locates Forge itself; change those two URLs to your plugin repositories. See Your first resource.

7. Publish the assets and the vendor resources

Upload the raw assets, then index and publish the resource archives Dassault ships. Publish raw assets covers both, including the resolution errors that are expected on a partially populated repository.

Next

Your repositories now hold everything a project needs. Every developer can follow Your first resource from here without repeating any of this.

On this page