stevedlawrence commented on issue #133: Enabled a few Calendar tests that now
work
URL:
https://github.com/apache/incubator-daffodil/pull/133#issuecomment-472202900
@jadams-tresys Commit 0b924b67de67 for DAFFODIL-2074 was able to reproduce,
track down, and fix issues related to locale.
Access granted.
- Steve
On 3/12/19 5:51 PM, Sloane, Brandon wrote:
> Can I have write access to the Apache Daffodil wiki. I am working on an
> updated proposal to add enum support to DFDL.
>
>
> My wiki account name is "Brandon Sloane" associated with this email,
> "bslo...@tresys.com"
>
>
Can I have write access to the Apache Daffodil wiki. I am working on an updated
proposal to add enum support to DFDL.
My wiki account name is "Brandon Sloane" associated with this email,
"bslo...@tresys.com"
Thanks,
Brandon T. Sloane
Associate, Services
bslo...@tresys.com | tresys.com
Josh Adams created DAFFODIL-2094:
Summary: TDMLRunner loads external file with different encoding
Key: DAFFODIL-2094
URL: https://issues.apache.org/jira/browse/DAFFODIL-2094
Project: Daffodil
Steve Lawrence created DAFFODIL-2093:
Summary: Cannot build and test daffodil in IntelliJ
Key: DAFFODIL-2093
URL: https://issues.apache.org/jira/browse/DAFFODIL-2093
Project: Daffodil
I'd prefer not to break out the CLI into a separate repo just because
IntelliJ not supporting sbt integration tests. It's nice to have the CLI
tightly integrated with everything else. It's also used for created
release, so being in a separate repo complicates that a bit.
This technique of using a
I've taken a look at what changes are necessary to support IntelliJ, and
found two main issues, both kindof related.
1. The first issue is our "debug" configuration. This is used to
separate tests that are known to fail from working tests, while still
allowing us to easily run failing tests via
