Publish BIRT Runtime to maven repository.

• JDK 21
• Apache Maven

Compile the project:

mvn compile

Run the publisher with the required parameters:

mvn exec:java \
  -Dmaven.repo.url=https://repo.example.com/birt \
  -Dmaven.username=username \
  -Dmaven.password=password

or, use repository id from settings.xml

mvn exec:java -Dmaven.repo.id=birt-repo -Dmaven.profile=birt-profile

to sign the artifacts with GnuPG:

export GPG_KEY=/path/to/gpg.key
export GPG_PASSPHRASE=TheBigSecret
mvn exec:java \
  -Dmaven.repo.id=birt-repo \
  -Dmaven.profile=birt-profile

to publish shapshots:

mvn exec:java \
  -Dmaven.repo.id=birt-repo \
  -Dmaven.profile=birt-profile \
  -Dmaven.snapshots=true

To deploy artifacts to a local repository (tmp/repo) for testing:

mvn compile exec:java

Run unit tests:

mvn test

Use the maven.group system property to specify a custom Maven group ID:

mvn compile exec:java -Dmaven.group=com.example.birt

• -Dmaven.repo.id=<id> - repository id
• -Dmaven.repo.url=<url> - repository url
• -Dmaven.repo.username=<username> - repository username
• -Dmaven.repo.password=<password> - reposotpry password
• -Dmaven.profile=<name> - maven profile to use
• -Dmaven.group=<com.example.birt> - custom group id
• -Dmaven.snapshots=true - whether to publish snapshots
• -Dmaven.resolve=true - resolve all artifacts and their dependencies

Use following environment variables to provide gnupg options:

• GPG_KEY_FILE=<file> - GnuPG key file
• GPG_PASSPHRASE=<password> - GnuPG passphrase to unlock the key
• GPG_FINGERPRINT=<hex> - the signing key finger print (to use key other than first one)

The application uses a configuration file to define artifact details, P2 update sites, and mapping rules. A sample configuration file:

{
  "details": [
    {
      "group": "org.eclipse.birt",
      "name": "technology.birt",
      "scm": "https://github.com/eclipse-birt/birt"
    },
    {
      "group": "org.eclipse.datatools.plugins",
      "name": "tools.datatools",
      "scm": "https://github.com/eclipse-datatools/datatools"
    }
  ],
  "sites": [
    {
      "name": "birt",
      "url": "https://mirrors.dotsrc.org/eclipse/birt/updates/release/4.19.0"
    },
    {
      "name": "datatools",
      "url": "https://mirrors.dotsrc.org/eclipse/datatools/updates/release/1.16.3"
    },
    {
      "name": "orbit",
      "url": "https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/release/4.35.0"
    }
  ],
  "mappings": [
    {
      "pattern": "(org\\.eclipse\\.(equinox|osgi)):.*",
      "groupId": "org.eclipse.platform"
    },
    {
      "pattern": "(org\\.eclipse\\.orbit):(derby):(.*)",
      "groupId": "org.apache.derby"
    },
    {
      "pattern": "(org\\.eclipse\\.birt\\.features):(org\\.eclipse\\.birt\\.engine\\.runtime):(.*)",
      "groupId": "org.eclipse.birt",
      "artifactId": "birt-runtime"
    },
    {
      "pattern": "org\\.apache\\.commons\\.net",
      "groupId": "commons-net",
      "artifactId": "commons-net",
      "version": "3.2"
    }
  ],
  "candidates": [
    { "pattern": "org\\.eclipse\\.birt.*" },
    { "pattern": "org\\.eclipse\\.datatools.*" },
    { "id": "org.apache.axis" },
    { "id": "org.eclipse.orbit.xml-apis-ext" },
    { "id": "uk.co.spudsoft.birt.emitters.excel" }
  ],
  "publish": [{ "id": "org.eclipse.birt.engine.runtime.feature.group" }]
}

1. The application scans all defined P2 update sites.
2. It constructs a dependency graph of installable units.
3. Maven coordinates are adjusted according to the mapping rules.
4. Artifacts are checked against Maven Central to avoid duplicate publishing.
5. Missing artifacts are downloaded, POM files are generated, and the artifacts are published to the specified Maven repository.
6. .feature.group artifacts are published as POM-type artifacts.
7. Corresponding source artifacts are identified and published where available.

• details – Metadata for POM generation (e.g., SCM information)
• sites – P2 update sites to scan
• mappings – Rules to adjust Maven coordinates
• candidates – Candiate units to publish
• exclude - Exclude units completely (even from dependencies)
• publish – List of units to publish

Besides the candiates units, we can force maven central check using -Dmaven.resolve=true property.