You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2018/01/16 20:39:00 UTC

[jira] [Resolved] (DAFFODIL-1869) Nato link16 doesn't work on 2.0.0 Daffodil

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

Michael Beckerle resolved DAFFODIL-1869.
----------------------------------------
       Resolution: Fixed
         Assignee: Dave Thompson  (was: Michael Beckerle)
    Fix Version/s:     (was: 2.0.1)
                   2.1.0

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)