Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add maven-metadata.xml to support version discovery // Automatic dependency updates #15

Open
b-heimann-senacor opened this issue Nov 6, 2024 · 0 comments

Comments

@b-heimann-senacor
Copy link

b-heimann-senacor commented Nov 6, 2024

I am using Maven to incorporate the one.talon:talon-one-client library into my Java application, exactly as outlined in the project's README.

I would now like to set up automatic dependency updates for my application using Renovate. Renovate is an automated tool that scans software repositories for dependencies, checks for newer versions, and then creates pull requests with these updates in the project's codebase. This automated process helps keep software projects up-to-date, thereby reducing technical debt and mitigating potential security vulnerabilities associated with outdated dependencies.

Renovate works without issues with standard Maven repositories like Maven Central, Artifactory, Nexus, etc.
However, it does not function with this GitHub repository: https://github.com/talon-one/maven-artefacts.

For Renovate to work, a Maven repository needs to provide maven-metadata.xml files. Essentially, this file is a list of all available versions of a Maven artifact present in the repository (see Maven Metadata > The A Level Metadata).
In this GitHub repository, the maven-metadata.xml file is missing (more specifically, the file https://github.com/talon-one/maven-artefacts/raw/master/one/talon/talon-one-client/maven-metadata.xml).

Could you add this maven-metadata.xml file? From my understanding, this is a standard feature of all Maven repositories.
Why aren't you using a real Maven repository such as GitHub Packages or Maven Central?

Edit:
I can see that there is a maven-metadata-local.xml file. Can't you just rename it?
According to https://maven.apache.org/ref/3.8.8/maven-repository-metadata/, the file should not have the -local suffix on remote repositories like this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant