+1 on the ".dar" SBT plugin.
Once a Daffodil Archive format is established, an SBT plugin enables
developers to easily create Daffodil Archives and further enforce
consistency.
On Mon, Jul 24, 2023 at 9:10 AM Davin Shearer wrote:
> +1 on the ".dar" idea.
>
> The Daffodil Archive ".dar" idea Ste
+1 on the ".dar" idea.
The Daffodil Archive ".dar" idea Steve introduced and the parallels with
the Apache NiFi ecosystem is exciting. The idea of bunding the serialized
parser, the runtime dependencies, and a README is a great non-intrusive
solution to both the tunables and classpath problems.
Do these products support saved parsers? I believe tunables are
serialized along with parser so if the tunables were set when built it
should work as expected, so wouldn't need a new Daffodil version to support.
If not, a top-level setTunable annotation seems reasonable to me. Though
I imagine
An issue has come up and I want to discuss a possible idea to help our
users manage this.
Products have embedded Daffodil.
Those products do not provide means for setting daffodil tunables.
But we know some of the tunables are important to enable a schema to work -
e.g., size limits on regex mat
