[
https://jira.codehaus.org/browse/MRELEASE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-453.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> wagon:upload fails when run from release:perform
> ------------------------------------------------
>
> Key: MRELEASE-453
> URL: https://jira.codehaus.org/browse/MRELEASE-453
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0-beta-9
> Environment: Maven 2.1.0
> Reporter: Trevor Harmon
> Attachments: pom.xml
>
>
> I'm using release:perform, and it works perfectly in the standard
> configuration. But now I'm trying to modify it so that an additional goal is
> invoked as part of the release:perform process. The additional goal is
> wagon:upload, which I've configured to upload some files to a server via SCP.
> I tested the wagon goal by running "mvn wagon:upload", and it worked fine.
> So, I simply added "wagon:upload" to the list of goals in the release:perform
> plugin. As expected, running "mvn release:perform -DconnectionUrl=..." starts
> the usual release:perform process, but now it fails at the end with an error:
> [INFO] [INFO] One or more required plugin parameters are invalid/missing for
> 'wagon:upload'
> [INFO]
> [INFO] [0] Inside the definition for plugin 'wagon-maven-plugin' specify the
> following:
> [INFO]
> [INFO] <configuration>
> [INFO] ...
> [INFO] <url>VALUE</url>
> [INFO] </configuration>
> [INFO]
> [INFO] -OR-
> [INFO]
> [INFO] on the command line, specify: '-Dwagon.url=VALUE'
> This is baffling because there are no errors when running wagon:upload
> directly. And I've checked and re-checked the plugin configuration. The <url>
> element is there, and it all looks good.
> I've attached the POM I'm using, with all of the extraneous stuff removed.
> I've also anonymized the SCM configuration, so it's not a repeatable test
> case, but otherwise it shows the exact configuration that triggers the error.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
