You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/12/10 19:13:00 UTC

[jira] [Assigned] (MDEPLOY-279) Missing validation of altDeploymentRepository mojo parameter

     [ https://issues.apache.org/jira/browse/MDEPLOY-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov reassigned MDEPLOY-279:
--------------------------------------

    Assignee: Michael Osipov

> Missing validation of altDeploymentRepository mojo parameter
> ------------------------------------------------------------
>
>                 Key: MDEPLOY-279
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-279
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy
>    Affects Versions: 3.0.0-M1
>            Reporter: Tamás Cservenák
>            Assignee: Michael Osipov
>            Priority: Major
>
> 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.3.4#803005)