Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: 2.7
-
Fix Version/s: None
-
Component/s: deploy:deploy-file
-
Labels:None
-
Environment:all
-
Patch Submitted:Yes
-
Number of attachments :
Description
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 :
<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>
while the following works fine :
<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>
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.
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