CATIA Magic 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 assets into an exact folder layout, 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.
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 archives with the layout CATIA Magic expects.
Validates inputs
Enforces versioning, metadata, structure and dependency rules before a build can produce something broken.
Publishes
Pushes resources, plugins and raw assets to your repositories, so downstream teams resolve them as ordinary Maven artifacts.
Requirements
CATIA Magic 2024x through 2026x · a JDK 17 or 21 per target version · Gradle 9 · Nexus, Artifactory or local hosting.
Interested in Forge?
Products ship to clients during an engagement. Tell us what you are building.