[jira] [Resolved] (DAFFODIL-2695) TDML test from CLI don't lookup model relative to DAFFODIL_CLASSPATH

["Josh Adams (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Adams resolved DAFFODIL-2695.
----------------------------------
      Assignee:     (was: Josh Adams)
    Resolution: Cannot Reproduce

Was unable to reproduce this issue following the provided directions.  The daffodil test command seems to be working correctly.

> TDML test from CLI don't lookup model relative to DAFFODIL_CLASSPATH
> --------------------------------------------------------------------
>
>                 Key: DAFFODIL-2695
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2695
>             Project: Daffodil
>          Issue Type: Bug
>          Components: TDML Runner
>    Affects Versions: 3.3.0
>            Reporter: Mike Beckerle
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> I discovere just today that in a parserTestCase if the model is defined relative to the src/main/resources directory, that it works fine for 'sbt test', but if you try to run that TDML via the daffodil CLI, it fails:
> {code:java}
> export DAFFODIL_CLASSPATH=src/main/resources:src/test/resources:src/test/scala
> daffodil test -iii src/test/resources/com/owlcyberdefense/skyview/skyview.tdml
> {code}
> That fails, unable to find the schema based on the model relative path. 
> The model path gets seems to get interpreted relative to the project homedir, not classpath relative. 
> If you change the model in the parserTestCases to be relative to the project root, by adding src/main/resources to the front of it then it works via 'sbt test', via IntelliJ idea, and at the daffodil CLI command. 
> I think this is a bug in the TDML runner as used by the CLI. One should not have to append src/main/resources to the front of the model path. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)