You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2022/05/10 18:47:00 UTC

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

Mike Beckerle created DAFFODIL-2695:
---------------------------------------

             Summary: 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


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.7#820007)