[
https://issues.apache.org/jira/browse/DAFFODIL-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327759#comment-16327759
]
Michael Beckerle edited comment on DAFFODIL-1869 at 1/16/18 8:43 PM:
---------------------------------------------------------------------
Fixed in Daffodil 02c8324294ed4395c1231c6ea3ec6ae77139ba46
The nato-stanag-5516 git hash (from DI2E.net) which works with this is:
fd53031c6e2e51b750f515bd01a4bedb48c14745 which is branch nato-20170602
was (Author: mbeckerle):
Fixed in
02c8324294ed4395c1231c6ea3ec6ae77139ba46
Tests added which insure one gets this warning, and the runtime SDE in
proper situations. See test_queryStyle1 and test_queryStyle2.
> 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)
