[
https://issues.apache.org/jira/browse/MDEPLOY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774968#comment-17774968
]
Jared Stehler commented on MDEPLOY-312:
---------------------------------------
I need to know what the resolved snapshot version was for project artifacts
which have been deployed to a remote repository during the build. We have a
custom artifact resolver which relies on this information being properly
published by builds.
The previous version of deploy-plugin did this by working directly with the
Artifact instances from the project model, updating them with resolved version.
Since moving to the aether deployer, this no longer occurs. I didn't see this
change in behavior called out in PR comments, so it seems like an inadvertant
change rather than explicit / desired.
Regarding the concern about pointing to non-existant local artifacts: the
project model Artifact class has support for this via `getBaseVersion()`.
> [REGRESSION] deploy no longer updates project model
> ---------------------------------------------------
>
> Key: MDEPLOY-312
> URL: https://issues.apache.org/jira/browse/MDEPLOY-312
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy, deploy:deploy-file
> Affects Versions: 3.0.0
> Reporter: Jared Stehler
> Priority: Major
>
> Prior to 3.0.0, the maven-deploy-plugin would update artifacts on the Project
> model:
> *
> [https://github.com/apache/maven/blob/master/maven-compat/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java#L147]
> *
> [https://github.com/apache/maven-deploy-plugin/blob/maven-deploy-plugin-2.8.2/src/main/java/org/apache/maven/plugin/deploy/DeployFileMojo.java#L276]
> This is no longer occurring with the migration to maven-resolver, which is
> breaking our downstream plugins relying on the resolved SNAPSHOT version.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
