You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lucas Lampietti (JIRA)" <ji...@codehaus.org> on 2012/06/19 15:28:21 UTC
[jira] (MDEPLOY-149) deploy-file fails with the element
containing spaces or line breaks
[ https://jira.codehaus.org/browse/MDEPLOY-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucas Lampietti closed MDEPLOY-149.
-----------------------------------
Resolution: Not A Bug
Forget this issue, cause filepath can contain some spaces, so trim is not a solution.
A simple workaround is to use the build-helper-maven-plugin:attach-artifact goal when necessary in POM and use the deploy-file goal only for command line
> deploy-file fails with the <files/> element containing spaces or line breaks
> ----------------------------------------------------------------------------
>
> Key: MDEPLOY-149
> URL: https://jira.codehaus.org/browse/MDEPLOY-149
> Project: Maven 2.x and 3.x Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
> Affects Versions: 2.7
> Environment: all
> Reporter: Lucas Lampietti
> Attachments: mvn-deploy.patch
>
>
> The deploy-file goal fails if we set a list of files with line breaks or spaces (for better readability since we have a long list of aside artifacts to deploy)
> The following sample fails :
> {code:xml}
> <configuration>
> <classifiers>
> classifier1, classifier2
> classifier3
> </classifiers>
> <files>
> ${basedir}/src/main/assets/artifact1.zip, ${basedir}/src/main/assets/artifact2.jar,
> ${basedir}/src/main/assets/artifact3.jar
> </files>
> <types>
> zip,
> jar, jar
> </types>
> </configuration>
> {code}
> while the following works fine :
> {code:xml}
> <configuration>
> <classifiers>
> classifier1, classifier2
> classifier3
> </classifiers>
> <files>
> ${basedir}/src/main/assets/artifact1.zip,${basedir}/src/main/assets/artifact2.jar,${basedir}/src/main/assets/artifact3.jar
> </files>
> <types>
> zip,
> jar, jar
> </types>
> </configuration>
> {code}
> As visible in these configuration samples, the elements <classifiers/> end <types/> are not affected and work fine even with spaces or line breaks in them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira