Hi,

I'm working on bringing Java build cross JDK versions to Jenkins. However,
I get stuck on BEAM-2164
<https://issues.apache.org/jira/browse/BEAM-2164> which
is running bash script failed though exec-maven-plugin. In order to have
cross-JDK builds on Jenkins, project directory contains space characters,
which breaks this bash script
<https://github.com/apache/beam/blob/master/sdks/java/maven-archetypes/examples/generate-sources.sh>
when
building beam-sdks-java-maven-archetypes-examples module.

I got following error log from build
<https://builds.apache.org/job/beam_PostCommit_Java_JDK_Versions_Test/jdk=JDK%201.8%20(latest),label=beam/6/console>
:

rsync: change_dir
> "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_JDK_Versions_Test/jdk\#012.\#012(latest)/label/beam/sdks/java/maven-archetypes/examples/../../../../examples/java/src/main/java/org/apache/beam/examples"
> failed: No such file or directory (2)


The problem happens in executing "mkdir -p "${ARCHETYPE_ROOT}/src/main/java"
". ${ARCHETYPE_ROOT} contains space character and the directory isn't
created. I run the script through commandline (without using mvn) and it
works perfectly. Looks like exec-maven-plugin handles this situation in
different ways, but I'm not the expert of Maven and play around commands in
the script doesn't help.

Currently I totally have no ideas. I'll be very appreciate if anyone can
provide some hint.

Thanks!
Mark

Reply via email to