[
https://issues.apache.org/jira/browse/MDEPLOY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775024#comment-17775024
]
Jonathan Haber commented on MDEPLOY-312:
----------------------------------------
There's a simple version that we open-sourced a while back available here:
https://github.com/HubSpot/maven-snapshot-accelerator
And accompanying blog post with more background:
https://product.hubspot.com/blog/speeding-up-maven-snapshots
Our internal version has picked up a variety of optimizations over time (For
example, skipping updates if the commit sha hasn't changed. And also the API
now generates and returns maven-metadata files directly, so once the build
starts all of the updated Maven snapshot metadata has already been written
directly into your local repo. And then the only thing we fetch from the remote
repo are the transformed snapshot versions which are immutable artifacts and
can be cached forever)
> [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)
