Forge
Develop, test, package and publish CATIA Magic resources with Gradle.
Forge is MBSE Consulting's Gradle plugin com.mbseconsulting.forge. A project applies it to build,
test, package and publish a CATIA Magic resource or plugin.
CATIA Magic — Cameo Systems Modeler, Magic Cyber Systems Engineer and their siblings — lets engineering teams extend the tool with custom resources: profiles, model libraries, templates, samples, custom diagrams, perspectives and compiled plugins. Building one by hand means zipping those assets into an exact folder layout, hand-writing two XML descriptors, keeping a CATIA Magic installation in step with the resources you depend on, and publishing the result. Forge automates that lifecycle, so a team writes the resource and lets the build handle the rest.
Who it is for
Forge serves engineers who develop CATIA Magic resources and plugins, and the administrator who sets up the Nexus or Artifactory repositories those resources publish to.
What it does
- Sets up the environment. Downloads and installs CATIA Magic, the matching JDK and JRE, and the resources a project depends on, from your own Nexus or Artifactory.
- Assembles deterministically. Generates both descriptors, patches MDZIPs, stages the tree, and packages the archives with the layout CATIA Magic expects.
- Validates inputs. Enforces the rules for versioning, metadata, structure and dependencies before a build gets far enough to produce something broken.
- Publishes. Pushes resources, plugins and raw assets to your repositories with consistent metadata, so downstream teams can resolve them as ordinary Maven artifacts.
- Fills Dassault's gap. Dassault ships no dependency resolver and no repository for resources. Forge treats resources and plugins as Maven artifacts and lets Gradle resolve them.
Requirements
| Component | Supported |
|---|---|
| CATIA Magic | 2024x through 2026x |
| Java | A JDK per target version — 17 or 21 |
| Gradle | 9.x, with a daemon JVM between 17 and 26 |
| Repository | Nexus or Artifactory, or local hosting |
Where to start
A first-time user starts with Your first resource, which goes from the project template to a published resource zip.
An administrator facing an empty Nexus or Artifactory starts with Bootstrap the repositories.
Key concepts
- Resource. An archive CATIA Magic installs: static assets in a fixed folder layout, described by a resource descriptor. One Git repository holds one resource, and that resource holds at most one plugin jar.
- Plugin. Compiled code CATIA Magic loads, described by a generated
plugin.xml. - Properties. Every Forge setting is a
com.mbseconsulting.forge.*key ingradle.properties, validated before the build gets far. - Dependencies. A resource can require other resources, a plugin can require other plugins and Java libraries. Forge publishes resources and plugins as Maven artifacts, so Gradle resolves the whole graph and Forge installs it in order.
The guide groups its pages by what you are doing: a tutorial teaches, a how-to guide solves one task, a reference page answers a lookup, and an explanation page gives the reasoning.