[
https://issues.apache.org/jira/browse/MDEPLOY-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965820#comment-17965820
]
Olivier Lamy commented on MDEPLOY-279:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#549|https://github.com/apache/maven-deploy-plugin/issues/549].
> Missing validation of altDeploymentRepository mojo parameter
> ------------------------------------------------------------
>
> Key: MDEPLOY-279
> URL: https://issues.apache.org/jira/browse/MDEPLOY-279
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 3.0.0-M1
> Reporter: Tamas Cservenak
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.0.0-M2
>
>
> Reproducer: [https://github.com/cstamas/mvn-md-bug]
> Command like: {{mvn clean deploy
> -DaltDeploymentRepository=localhost-nexus::default::http://localhost:8081/content/repositories/snapshots/}}
> (w/ 3.0.0-M1 m-d-p, needs POM edit)
> As seen in MDEPLOY-274, m-d-p 2.x succeeds, while 3.x fails with _same CLI
> command line_.
> True, the parameter did change between 2.x and 3.x, still IMO validation is
> missing: 3.x should either fail early (not at attempted deploy w/o
> credentials) or at least WARN about "not recognized parameter", or best.
> accept 2.x format as well, but only if layout is "default".
> Maybe some other changed parameters needs some validation as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
