[ 
https://issues.apache.org/jira/browse/MDEPLOY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775036#comment-17775036
 ] 

Tamas Cservenak commented on MDEPLOY-312:
-----------------------------------------

THIS is very cool! Thanks! Will dive into that a bit, as I was also tinkering 
about several things (one is mentioned on some other JIRA, basically stop using 
"snapshot normalization" [rename downloaded timestamped snapshot files into 
-SNAPSHOT files, effectively making all local repository content immutable]), 
and this "warming up" the local repository....

> [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)

Reply via email to