Created https://issues.apache.org/jira/browse/DAFFODIL-2617 for this
documentation issue.
On Fri, Dec 31, 2021 at 10:16 AM Mike Beckerle wrote:
> This combination works: Java 11, Scala 2.12.11, Daffodil 2.7.0
>
> Using scala 2.12.11 has the further implication that one cannot use Java
> 17 as
This combination works: Java 11, Scala 2.12.11, Daffodil 2.7.0
Using scala 2.12.11 has the further implication that one cannot use Java 17
as Java 17 requires scala version 2.12.15.
We probably need to add a matrix of this compatibility to our releases main
page.
On Fri, Dec 31, 2021 at 8:46 AM
Yes, this sounds very familiar.
We had a pull request from Scala steward to updated scala to from
2.12.11 to 2.12.13 which triggered what I think is the same bug:
https://github.com/apache/daffodil/pull/505
Based on some of my comments in the PR, I tracked it down to a change in
Scala
I have a test failing that I'm running against Daffodil 2.7.0. I'm
developing a large schema for a big obscure data format.
I need the schema to work on Daffodil 2.7.0, so I'm hoping to find a
workaround.
The bug does not occur in Daffodil 3.2.1.
The issue seems related to the TDML runner's
