You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2023/06/05 22:13:00 UTC

[jira] [Closed] (DAFFODIL-2816) Saved parser version checks against application version, not Daffodil version

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

Dave Thompson closed DAFFODIL-2816.
-----------------------------------

Verified the specified commit (commit 587bae4474d746395c21be7070aa6e6063e84479) is included in the latest pull from the daffodil repository.

Verified, via review, changes identified in the commit comment were implemented. 

Verified the affected daffodil subproject sbt test suites executed successfully.

Verified the Version file is created in the fix commit and not in the pre-fix commit.

> Saved parser version checks against application version, not Daffodil version
> -----------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2816
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2816
>             Project: Daffodil
>          Issue Type: Bug
>            Reporter: Josh Adams
>            Priority: Major
>             Fix For: 3.5.0
>
>
> I wrote a small test program to handle large number of files that calls the Daffodil Scala API.  It loads a saved-parser to handle the processing.  When the program is packaged into a jar file and run with "java -jar" Daffodil attempts to check the version in the saved parser file against the version of the program calling Daffodil, which in my case is 0.0.1 and then obviously fails the check.
> We need some way to check against the version of Daffodil that the program is linked against instead of the version of the program itself.



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