Fix pipeline failing due to maven issues

[omarsilva1]

Describe the bug As mentioned in https://github.com/International-Data-Spaces-Association/DataspaceConnector/issues/678 and https://github.com/International-Data-Spaces-Association/DataspaceConnector/pull/679, it is currently not possible to build the DSC with the latest maven version. This is due to maven not accepting HTTP urls since version 3.6. Furthermore, the version of the eis-ids repositories we are currently importing use HTTP. See the screenshot below: This breaks the pipeline, since github is currently using maven 3.9 for the actions. (See https://github.com/actions/runner-images/issues/7216)

Local Fix It is still possible to build the DSC locally when using maven 3.6.

Pipeline Fix Ideas This would possibly be fixed if we upgraded to the latest eis-ids version, but this would require changes in DSC code. By adding maven mirros (https://github.com/International-Data-Spaces-Association/DataspaceConnector/pull/681) I get a connection timed out message.

[nuthub]

Isn't it possible to push the affected artifacts to mvnrepository.com? This probably

• would restore buildability of older tags,
• would allow you to build the project with newer Maven versions and
• does not require to modify the Dockerfile as suggested here: https://github.com/International-Data-Spaces-Association/DataspaceConnector/pull/680
• would heal existing projects relying on a specific DSC version

Although I think that Maven searches all known repositories for dependencies until the searched artifact is found, I am not sure, if Maven still complains about an unavailable repository, even if it is not required to access it.