[
https://issues.apache.org/jira/browse/DAFFODIL-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2592.
-----------------------------------
Verified the specified commits (commits
0029591b643c191ea0156dd830e848e7f8a3e728 and
08c5a7ba412ace8c1b5847ed6e12abe85af78ae1) are included in the latest pull from
the daffodil repository.
Verified changes specified in the commit comment were implemented, by review.
Verified all effected daffodil sub-project sbt test suites executed
successfully.
Verified the nightly test schemas compile and save successfully.
Verified the nightly test suite executes successfully, single iteration.
> Move the daffodil_program_version variable outside of generated_code.c
> ----------------------------------------------------------------------
>
> Key: DAFFODIL-2592
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2592
> Project: Daffodil
> Issue Type: Bug
> Components: Back End C-Generator
> Reporter: Steve Lawrence
> Priority: Major
> Fix For: 3.3.0
>
>
> Currently, runtime2 writes the daffodil version to generated_code.c. We store
> some example generated_code.c files in the repo as examples, which means when
> we bump the Daffodil version number we must also remember to update these
> examples. That's not hard and we do have github checks to ensure they are
> updated, but it's one more thing to think about during the release process.
> We should move this version number somewhere else so we don't need to modify
> these example files for a version bump.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
