Define Maven and Artifactory repositories in projects' pom.xml

[yanavasileva]

Acceptance Criteria (Required on creation)

• Scope: camunda-bpm-platform camunda-bpm-platform-maintenance camunda-bpm-platform-ee camunda-bpm-platform-ee-maintenance upstream/downstream check sub modules to clean fix-maven-snapshots-issue-with-nexus
• Repositories Maven Central and public/internal Artifactory rpa and platform-ee where the license-book-generator is used - pluginRepository is needed.

      <repository>
        <id>maven-central</id>
        <name>Maven Central</name>
        <url>https://repo1.maven.org/maven2</url>
        <snapshots>
          <enabled>false</enabled>
        </snapshots>
      </repository>
      <repository>
        <id>camunda-nexus</id>
        <name>Camunda Nexus</name>
        <url>https://artifacts.camunda.com/artifactory/internal</url> <!-- "public" where applicable -->
      </repository>
    </repositories>

• Outcome Local build should not require profile activated by default in the maven settings.xml (local-build) No more warnings in the local builds: [WARNING] Could not transfer metadata org.camunda.bpm:camunda-engine:7.19.0-SNAPSHOT/maven-metadata.xml from/to fix-maven-snapshots-issue-with-nexus (allow-parent-pom-resolving-when-snapshot) ** CI builds should not be affected by the made changes

Hints

Links

• related to https://github.com/camunda/camunda-bpm-platform/issues/3197

Breakdown

### Tasks
- [ ] https://github.com/camunda/camunda-bpm-platform/pull/3246
- [ ] https://github.com/camunda/camunda-bpm-platform/pull/3271
- [ ] https://github.com/camunda/camunda-bpm-platform-ee/pull/785
- [ ] https://github.com/camunda/camunda-bpm-platform-ee/pull/791
- [ ] https://github.com/camunda/camunda-bpm-release-parent/pull/10
- [ ] https://github.com/camunda/camunda-spin/pull/185
- [ ] https://github.com/camunda/camunda-spin/pull/186
- [ ] https://github.com/camunda/camunda-spin/pull/187
- [ ] https://github.com/camunda/camunda-spin/pull/188
- [ ] https://github.com/camunda/camunda-connect/pull/79
- [ ] https://github.com/camunda/camunda-connect/pull/80
- [ ] https://github.com/camunda/camunda-commons/pull/31
- [ ] https://github.com/camunda/camunda-commons/pull/32
- [ ] https://github.com/camunda/camunda-commons/pull/33
- [ ] https://github.com/camunda/camunda-template-engines-jsr223/pull/27
- [ ] https://github.com/camunda/camunda-bpm-license-book-generator-ee/pull/15
- [ ] https://github.com/camunda/camunda-bpm-xslt-ee/pull/4
- [ ] https://github.com/camunda/camunda-bpm-rpa-bridge-ee/pull/79
- [ ] https://github.com/camunda/camunda-bpm-rpa-bridge-ee/pull/80
- [ ] https://github.com/camunda/camunda-bpm-rpa-bridge-ee/pull/81
- [ ] https://github.com/camunda/camunda-bpm-rpa-bridge-ee/pull/82
- [ ] https://github.com/camunda/camunda-bpm-platform-maintenance/pull/969
- [ ] https://github.com/camunda/camunda-bpm-platform-maintenance/pull/970
- [ ] https://github.com/camunda/camunda-bpm-platform-maintenance/pull/971
- [ ] https://github.com/camunda/camunda-bpm-platform-ee-maintenance/pull/397
- [ ] https://github.com/camunda/camunda-bpm-platform-ee-maintenance/pull/398
- [ ] https://github.com/camunda/camunda-bpm-platform-ee-maintenance/pull/399
- [ ] https://github.com/camunda/camunda-bpm-platform-ee-maintenance/pull/400
- [ ] https://github.com/camunda/camunda-bpm-platform-ee-maintenance/pull/401
- [ ] https://github.com/camunda/camunda-bpm-platform-ee-maintenance/pull/402

Dev2QA handover

• [ ] Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[yanavasileva]

Decision:

• define the repositories in camunda-bpm-release-parent so projects that inherit the parent, inherit the maven repositories as well. (Only examples and get-started don't inherit the release parent.)

[yanavasileva]

To Reviewer, I want to request feedback for

• the release parent so I can release it then and test the changes on ci as well.
• the platform and platform-ee clean up so I can create the branches

Please refer to Outcome for expectations when the local builds are run with the suggested changes

Local build should not require profile activated by default in the maven settings.xml (local-build) No more warnings in the local builds: [WARNING] Could not transfer metadata org.camunda.bpm:camunda-engine:7.19.0-SNAPSHOT/maven-metadata.xml from/to fix-maven-snapshots-issue-with-nexus (allow-parent-pom-resolving-when-snapshot) ** CI builds should not be affected by the made changes

Then the local-build profile can be deactivated and use only for examples where with test with SNAPSHOT artifacts.

[yanavasileva]

Hint how to list maven repositories (doesn't cover pluginRepositories): mvn dependency:list-repositories

[mboskamp]

Looks good 👍 Let's release the release parent and check CI.

[yanavasileva]

Current progress:

• camunda-bpm-release-parent version 2.2.6 has been released.
• CI is triggered for CE and EE
• Reviews for sideprojects are pending.

[yanavasileva]

To reviewer: Assigning for a review for platform and maintenance repos

[yanavasileva]

TODO:

• [x] document findings for platform multi module inheritance - root pom contains the default, all others (jboss, spring) are in parent
• [ ] inform the team

[yanavasileva]

Decisions:

• Include the default repositories to the root pom wherever repositories are defined. The order of repositories does matter. If some repositories are listed, e.g. JBoss and Spring, the release parent cannot be found to populate the default repositories. So we aim to have Maven Central and then Artifactory internal at the top.