[
https://issues.apache.org/jira/browse/DAFFODIL-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-1869.
-----------------------------------
Verified the latest updates from the incubator-daffodil repository included the
specified commit, 02c8324294ed4395c1231c6ea3ec6ae77139ba46. Verified the
automatic data pull script pulled the latest update to the nato-stanag
repository which included the associated commit.
Executed the nightly nato-stanag tests, which were failing due to previous
daffodil updates. The parse test now pass as expected. The unparse tests failed
due to changes in the nato-stanag schema which rendered the existing infoset
test files incorrect. Re-parsed the original test data files recreating the
infoset test files. Reran the nightly nato-stanag unparse test and they now
pass as expected.
> Nato link16 doesn't work on 2.0.0 Daffodil
> ------------------------------------------
>
> Key: DAFFODIL-1869
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1869
> Project: Daffodil
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Michael Beckerle
> Assignee: Dave Thompson
> Priority: Blocker
> Fix For: 2.1.0
>
>
> From NATO NCIA:
> Are you still planning to release a patch? The last Daffodil revision that
> was working is 3e754f259cbe9c36d96379921bc060acc4f8ab24 (23rd of May 2017).
> In later revisions, the compilation of the Link 16 schema is going wrong at
> J7.5I regarding the choice on "ActionIffSifManagement_1606-006 and the choice
> on "ModeICodeApplicability_1610-001".
> Reproducing this requires access to the Link16 schema, which requires access
> to DI2E.net DFDL/Daffodil project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
