Hi,

I'm encountering an issue while trying to build OpenVPMS (version 2.4.0.7-SNAPSHOT) using Maven. The build fails during the dependency resolution step, specifically when trying to download the artifact `com.atlassian.plugins:atlassian-plugins-framework-bundles:zip:spring50x:5.0.2`.

### Error Details:

The Maven build is unable to resolve the dependency `com.atlassian.plugins:atlassian-plugins-framework-bundles:zip:spring50x:5.0.2`, and several repositories (including `https://repository.openvpms.org/releases`, `https://repo1.maven.org/maven2`, `https://packages.atlassian.com/mvn/maven-external/`, etc.) are being queried without success. The error suggests that the artifact is either missing or there is an issue with accessing the repositories.

Here’s the relevant section from the build output:

```

[ERROR] Failed to execute goal on project openvpms-plugin-framework-bundles: Could not resolve dependencies for project org.openvpms:openvpms-plugin-framework-bundles:pom:2.4.0.7-SNAPSHOT

[ERROR] dependency: com.atlassian.plugins:atlassian-plugins-framework-bundles:zip:spring50x:5.0.2 (compile)

[ERROR] com.atlassian.plugins:atlassian-plugins-framework-bundles:zip:spring50x:5.0.2 was not found in https://repository.openvpms.org/releases during a previous attempt.

[ERROR] Could not transfer artifact from/to atlassian-public (https://packages.atlassian.com/mvn/maven-external/): Checksum validation failed, no checksums available.

...

```

### Troubleshooting Steps Taken:

- I’ve attempted to clear the Maven cache and re-run the build.

- I tried updating the repositories in `pom.xml` to ensure they are correctly configured.

- I’ve forced updates using `mvn clean install -U`, but the issue persists.

### Possible Causes:

- The artifact might be missing from the repository or incorrectly configured in the Maven settings.

- There could be an issue with repository access permissions or network configurations.

### Request for Assistance:

I would appreciate any insight or suggestions on the following:

1. Has anyone encountered a similar dependency resolution issue with `atlassian-plugins-framework-bundles` or other dependencies in the past?

2. Are there any recommended solutions or workarounds for resolving this particular dependency issue?

3. Should we consider adding alternate repositories or a proxy to ensure that the required artifacts are available?

Any help or suggestions would be greatly appreciated.

Thanks in advance for your assistance!

Best regards,

Anthony Matthews