Description
Tamas Cservenak opened MDEPLOY-296 and commented
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.
Issue Links:
- MDEPLOY-200 deployAtEnd fails if the last project to build skip deployment
("fixes") - MDEPLOY-204 Must deploy maven-metadata.xml last
("fixes") - MDEPLOY-226 DeployAtEnd fails when module has extension
("fixes") - MDEPLOY-295 Drop MAT
("fixes")
Remote Links: