Thanks for the review John.
> Then how do you combine your forked Daffodil and sample schemetron
> implementation/application together so that your simplest usage example
> actually works?
Sure. The missing instructions are below and they were also added to the
readme in the sample app repo.
+1 from me.
Sounds like Spark isn't an issue anymore.
Also, note that the last time there was a Scala 2.11.x release was
2.11.12 at the end of 2017 [1]. So there's been plenty of time for tools
to upgrade. And it sounds like there are no plans to create a 2.11.13
release [2].
- Steve
[1] https
There's actually some code-conditionalizations for 2.11 vs. 2.12 that would be
able to go away if we get rid of 2.11, which would be an added benefit.
I would support getting rid of 2.11.
I did use an apache zeppelin notebook with Daffodil that needed 2.11. It was
required to use 2.11 because i
I'd like to ask the Apache Daffodil developers to weigh on this question:
Does Daffodil need to run on Scala 2.11 anymore?
I've been told the only reason why we're still publishing Scala 2.11 builds is
for Apache Spark, which had been working only on Scala 2.11 for a long time
e
Welcome!
Yes, Daffodil certainly feels like it would be a good solution to your
problem.
Regarding incubation, Daffodil currently follows all the quality
standards and development practices that the Apache Software Foundation
requires and depends on that makes their projects successful. The main
Yeah, codecov doesn't have the greatest UI. I suggest we just turn on
the PR comments and see how it goes. If we find it spammy or not
helpful, we can see if we can configure it to make it more useful, or
just disable it again and better document it so that it's more visible.
On 9/29/20 2:57 PM,
