[
https://issues.apache.org/jira/browse/DAFFODIL-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747041#comment-17747041
]
Steve Lawrence commented on DAFFODIL-2707:
------------------------------------------
This is likely fixed as part of DAFFODIL-2381. That fix changed how CLI
integration paths are used, always keeping the binary path and arguments in a
Seq, along with a new "args" string interpolator to support paths with spaces.
It also uses a ProcessBuilder or Thread using that Seq, so at no point should
spaces be treated as an argument separator when executing a CLI test, like
might happen if we instead converted the Seq to a string and ran it in a shell.
We should reverify if this is still an issue and resolve it we cannot reproduce
it.
> Integration tests fail when DAFFODIL_HOME path includes spaces
> --------------------------------------------------------------
>
> Key: DAFFODIL-2707
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2707
> Project: Daffodil
> Issue Type: Bug
> Components: QA
> Affects Versions: 3.3.0
> Reporter: Steve Lawrence
> Priority: Minor
> Labels: beginner
>
> Steps to reproduce
> {code:bash}
> export DAFFODIL_HOME="/tmp/path with spaces"
> mkdir "$DAFFODIL_HOME"
> cd "$DAFFODIL_HOME"
> git clone https://github.com/apache/daffodil.git
> cd daffodil
> sbt IntegrationTest/test
> {code}
> Note that if the path to your daffodil repo path has spaces but you don't set
> DAFFODIL_HOME, then tests work correctly. Unfortunately, sometimes this is
> required, like when using certain IDE's.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
