[
https://issues.apache.org/jira/browse/MDEPLOY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774992#comment-17774992
]
Tamas Cservenak commented on MDEPLOY-312:
-----------------------------------------
Yes, all correct. You need to register your listener somehow, most recommended
way is from an extension.
Re extensions: I hope you are aware that enlisting extensions in
{{.mvn/extensions.xml}} is possible (then Maven resolves and uses enlisted
extensions along with dependencies), and is actually much cleaner, than using
"custom distributions" (or mutilating existing distributions by dropping stuff
into {{/lib}} of Maven). Unless, there is some technical obstacle, not allowing
you to use former way. See
https://maven.apache.org/configure.html#mvn-extensions-xml-file
So, IMHO the "reporter" side could be a plain extension, that does just that:
listens to deploy events, and reports those to API (maybe some config to narrow
reported groupIds or alike, exclude them?)
This sounds interesting, too sad is not open....
> [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)
