Service should use only Community Maven Repositories
pom.xml
files should point to only Community repositories.
In the current state several pom.xml
files point to non-Community Maven Repositories.
Example (src/pom.xml
, lines 192+):
<distributionManagement>
<repository>
<id>dspdm-release</id>
<name>dspdm-release</name>
<url>https://repo.ds365.ai/artifactory/dspdm-maven-release</url>
</repository>
<snapshotRepository>
<id>dspdm-snapshots</id>
<name>dspdm-snapshots</name>
<url>https://repo.ds365.ai/artifactory/dspdm-maven-snapshots</url>
</snapshotRepository>
</distributionManagement>
Example (src/dspdm.msp.mainservice/pom.xml
, line 52-53, but used as property in other parts of file):
<release.url>https://artifacts.repo.openearth.community/artifactory/distservices-maven-staging</release.url> <snapshot.url>https://artifacts.repo.openearth.community/artifactory/distservices-maven-snapshots</snapshot.url>
To make service compliant with the Community approach, please do the following:
-
Add
.mvn
folder with correct profile settings. Examples can be found in other Java services such as Storage (https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/.mvn/community-maven.settings.xml) or Search (https://community.opengroup.org/osdu/platform/system/search-service). Note the project id in the following URL types:https://community.opengroup.org/api/v4/projects/**44**/packages/maven
. It should be configured to id of current repository (id of current project is 1245). -
Remove any references to non-Community repositories inside
pom.xml
files. Examples of pom.xml files can be found in other Java-based services (e.g. here) -
Each pom.xml should be configured so each artifact is published to Community Maven repository. References to this logic can be also found in other Java-based services.
Additional information on how Maven building and publishing jobs are configured in CI/CD can be found here: https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/blob/master/build/maven.yml