RE: Validator SPI proposal

2020-09-29 Thread Interrante, John A (GE Research, US)
Hello John, Using ServiceLoader looks reasonable. I looked at your reference implementation and sample application, but can you clarify a question for me? First you build your forked Daffodil and your sample application separately in different directories. Then how do you combine your forke

Turn back on emails from coverage.io

2020-09-29 Thread Interrante, John A (GE Research, US)
Nice, clicking the badge on the main GitHub page takes me to the codecov report. Not so nice, the codecov UI doesn't give me something I can act on easily since I'm not familiar with codecov reports and they're not very intuitive. This leads me to reserve judgment how useful a codecov email mi

First Contact

2020-09-29 Thread COOPER, DARREN K GS-14 USAF AFMC 96 RNCS/RNCDR
Greetings, This is my first contact with any open source community, so please forgive my ignorance. I am working with a team, trying to solve a problem for the US Department of Defense (DOD), which I think Daffodil is a candidate solution. Here is a short synopsis: 1. A contractor dev

Validator SPI proposal

2020-09-29 Thread Wass, John L
Greetings, Please consider the following proposal to extend the Daffodil Infoset Validation API. The proposed changes support deploying custom validation implementations that are not built as part of the Daffodil distribution but are instead made available at runtime as Java Service Provider I

Re: Turn back on emails from coverage.io

2020-09-29 Thread Steve Lawrence
All seem like reasonable suggestions to me. Currently the only place the coverage is really visible is the badge we have on the main github page https://github.com/apache/incubator-daffodil I think all we need to do is delete/modify this config: https://github.com/apache/incubator-daffodil/blob/