You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "lbruun (via GitHub)" <gi...@apache.org> on 2025/03/28 16:31:18 UTC
[I] Separate "resolve" repo from "target" repo config [maven-deploy-plugin]
lbruun opened a new issue, #122:
URL: https://github.com/apache/maven-deploy-plugin/issues/122
### New feature, improvement proposal
Background: The plugin needs to update the `maven-metadata.xml` file. Hence it needs to download it from somewhere. This is what I call the "resolve" repo. It is usually the same as the "target" repo. But not in every case.
Suppose the requirement is to use the plugin solely to create local copy of what will (at a later stage) be uploaded to the target repo. Hence, we have:
```xml
<properties>
<altDeploymentRepository>local::file:./target/staging-deploy</altDeploymentRepository>
</properties>
```
The above setup will (AFAIK) attempt the download the `maven-metadata.xml` file from the above file URL. No such file will be present so it will assume that this is the first version of the GAV to be uploaded and it will therefore create the metadata file accordingly. Which is wrong.
I believe that what we need is a config knob that allows to use another URL for "resolve" of the metadata vs the URL where the upload happens.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org