[jira] [Commented] (MDEPLOY-296) Cleanup the plugin

["Hudson (Jira)" <ji...@apache.org>]

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

Hudson commented on MDEPLOY-296:
--------------------------------

Build failed in Jenkins: Maven » Maven TLP » maven-deploy-plugin » master #10

See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-deploy-plugin/job/master/10/

> Cleanup the plugin
> ------------------
>
>                 Key: MDEPLOY-296
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-296
>             Project: Maven Deploy Plugin
>          Issue Type: Task
>            Reporter: Tamás Cservenák
>            Assignee: Tamás Cservenák
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Original plugin made hoops and loops, instead to perform what it needed to perform. Partly to blame this was unfinished state of MAT API (it was able to install project only).
> Deploying project is needed in DeployMojo, but DeployFileMojo was forced to make hoops and loops due this, as it was passed one file (and maybe pomFile), and it was forced to create "fake" project, decorate and fake setup it with all whistle and bells, only to get it via MAT to resolver that would "decompose" it back into set of artifacts needing a deploy. So it went this file-artifact-project-artifact route, that made all the logic fragile and overly complicated.
> This PR completely reworks m-deploy-p making it (almost trivially) simple: it does what it needs to do, without any fuss, and does it in streamlined way: No fuss, no magic, no fake project building etc.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)