I support just modernizing the current KEYS file, not worrying about people
getting a failure when validating older releases using a newer KEYS file.
Instructions on how to validate could point this out, i.e., that KEYS
technology has changed so older releases require older KEYS files
Our quarterly board report is due shortly.
I think the big thing this quarter was our VSCode Extension 1.1.0 release.
If there are other things worth mentioning (at the level of the ASF board)
please remind me.
This is due early next week, so I'll hope for feedback no later than
Congratulations to all contributors of this important release. Well done.
I'll repeat the announcement over on the mailing lists like dfdl...@ogf.org,
the news page for that, etc., over the next few days.
On Wed, Aug 24, 2022 at 8:48 AM Shane Dell wrote:
> The Apache Daffodil community is
o hyphens or
periods allowed.
This sourcecode library is super cool. Has the ability to get the file
name, line number, enclosing class, enclosing definition, whether it is
val, lazy val, or def, etc.
It's all pretty easy to use.
- Mike Beckerle
e validate the
> sender's email address before clicking on links or attachments as they may
> not be safe.
> >
> > This is correct.
> >
> > Though Shane is a PMC, so he can vote and count as the third. Should
> have added an explicit +1 and added his name to the pass
s://lists.apache.org/thread/m4tc565t84fo2mwpxvgyr4qqmg9tgv37
>
> The vote breakdown is:
>
> +1 Mike Beckerle (binding)
> +1 Steve Lawrence (binding)
>
> Thanks to everyone who voted!
>
First off. Nice work! This is a big step forward from v1.0.0 and very
usable it seems.
Below is details I wrote down from my testing.
Tests I did:
git cloned ethernetIP DFDL Schema from DFDLSchemas on github.
sbt test - works
sbt publishLocal
git cloned PCAP from DFDLSchemas on github
sbt
+1 from me.
I did not examine this release for any of the formal requirements
(licenses, depenency info, etc.).
I just looked at it from functional QA perspective.
I installed and tested this on the PCAP schema from github DFDLSchemas.
This requires a component schema which is also at
that?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
-1 binding
Shane confirmed that the launch config wizard is broken.
On Fri, Jul 29, 2022 at 1:10 PM Mike Beckerle wrote:
> I'd like to request more time for this vote.
>
> I have only limited time today to check this release out, and limited
> connectivity today as I am on Amtrak
t Daffodil Debugger, configure launch.json but I get:
[image: image.png]
(btw: what is 'launch.config'? Shouldn't that say 'launch.json'?)
So something is up environmentally; I can't even test out the features yet.
-mike beckerle
On Wed, Jul 27, 2022 at 2:21 PM Shane Dell wrote:
> Hello
Current state of the wiki for the daffodil-vscode repo is supposed to be
that anyone with a github account can create/edit/whatever to it.
But I tested it today, and it fails... so created
https://issues.apache.org/jira/browse/INFRA-23492 to hopefully get this
fixed.
On Wed, Jul 20, 2022 at
don't feel
> strongly either way, though I lean towards including in the repo).
> Comments inline.
>
> On 7/20/22 9:04 AM, Mike Beckerle wrote:
> > I think putting dap into the main daffodil repo is a false economy.
> > Consider:
> >
> > 1) more sbt hacks to e
; different versions of Daffodil without having to install a different
> extension.
>
> On 7/19/22 4:10 PM, Mike Beckerle wrote:
> > I am leaning toward a separate repo (called daffodil-dap-server) which
> uses
> > (depends on) daffodil.
> > (btw: what does DAP stand for again? D
plan accordingly, that shouldn't be too much of an issue.
> >
> > I would perfer this approach over creating a new repo. It's a bit less
> > to keep track of, and makes it easier to ensure we don't have any
> > breaking changes with changes to Daffodil.
> >
> > On
.
>
> I would perfer this approach over creating a new repo. It's a bit less
> to keep track of, and makes it easier to ensure we don't have any
> breaking changes with changes to Daffodil.
>
> On 7/19/22 1:52 PM, Mike Beckerle wrote:
> > I think of this as a daffodil server mode
I think of this as a daffodil server mode, for the front end VSCode stuff
to use.
So, is it plausable to add the code to daffodil proper. Make it a CLI
command mode to start up this server, so that
daffodil vscodeServer
starts it, optionally with connection options like what ports to use,
ed on this earlier that Exificient does have a StAX API and is worht
> investigating due to the performance overhead of SAX when unparsing.
>
> * Examples should show both file-of-data mode, and streaming mode (many
> messages on unbounded input)
>
> * CLI exi feature mus
Mike Beckerle wrote:
> This email thread for discussion of EXI capabilities for Daffodil.
>
> The primary requirement is improved performance by avoiding the processing
> and size overhead of XML (or JSON) textual infoset output creation from
> parsing, and input to unparsin
This email thread for discussion of EXI capabilities for Daffodil.
The primary requirement is improved performance by avoiding the processing
and size overhead of XML (or JSON) textual infoset output creation from
parsing, and input to unparsing.
Users want to process large binary data files
fodil CLI tool can kill 2 birds with one stone in that we will be
> adding support for EXI as well as demonstrating how to pass in your own SAX
> ContentHandler.
> >
> > Josh
> >
> > From: Mike Beckerle
> > Sent: Monday, July 11,
(I am breaking this discussion out of a bot PR thread to discuss more
broadly.)
Steve Lawrence reminded us recently that updates need to be reviewed
relative to a checklist:
https://cwiki.apache.org/confluence/display/DAFFODIL/Scala+Steward
Given the amount of work this implies, per update,
at section.
Is this feasible from javascript executing in the browser?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
Anybody else think the bot-based updates are far too frequent?
What if we restricted this to monthly?
I'd like to find out earlier about security-related issues, but otherwise,
I'd really like to see these things less often.
But I'm curious of others' view.
Message ID:
tly an API and I can't think of an easy way to pass a
> SAX ContentHandler over the command line. Adding an EXI option to the
> Daffodil CLI tool can kill 2 birds with one stone in that we will be adding
> support for EXI as well as demonstrating how to pass in your own SAX
> ContentHandl
In the CLI, there is the -I option to specify infoset-type.
One of the choices is 'sax'.
This is a mistake I think. This is really "XML text by way of calling the
SAX API". It's effectively a testing mode for us.
SAX usage is inherently an API.
I believe we should remove this feature from the
The upgrade bots will probably nag us about this.
We still have to wait for some libraries (scala-xml at least) before we can
upgrade to this, but we should plan for the right time.
Perhaps we just wait for 2.12.17 which is planned for within a few months
due to a regression that was discovered?
Last time I did DFDL training I gave a demo of the VSCode v1.0.0 debugger.
Are there new features/fixes since then on the current SNAPSHOT branch that
are stable enough that I should incorporate them into the next training I
do later in July? (July 26, 27, 28 specifically)
? If you run mvn -v does it tell you
> what java version is being used? You might try an older Java version. I
> think I've had issues in the past where mvn need to be run with an older
> version of Java.
>
> On 6/16/22 4:15 PM, Mike Beckerle wrote:
> > I wanted to see if
I wanted to see if these worked with Daffodil 3.3.0
I can't get the build instructions to work, even for the existing Daffodil
3.1.0 version the Maven pom.xml files have.
$ mvn install
[ERROR] Error executing Maven.
[ERROR] java.lang.IllegalStateException: Unable to load cache item
[ERROR]
Is there a basic technique I can put in my ~/.gitconfig so that my daffodil
repo clone won't show dependabot and scala steward branches?
Basically, I don't want to fetch info about commits that have "dependabot"
in their remote branch name. For any remote.
E.g., see screenshot here from qgit:
Comments are welcome, but are needed by end of day (ET.US) on Monday June
6.
---
## Description:
The mission of Apache Daffodil is the creation and maintenance of an
implementation of the Data Format Description Language standard
and related software used to
Davin, How would you like this feedback.
Should I add directly to the wiki page?
On Fri, May 13, 2022 at 2:49 PM Shearer, Davin wrote:
> Hello Apache Daffodil developers,
>
>
> Now that the Apache Daffodil VS Code Extension version 1.0.0 has been
> released (get it now on the Microsoft® VS
and builds the
new code base, and then tests the new/changed features?
Or are you expecting just code-scrutiny for advice on patterns/idioms,
likely errors, etc.?
Please let's discuss.
-mike beckerle
Just takes an abstract.
You can submit an abstract without having a commitment that you can attend
the conference. If it turns out you cannot, your talk can be cancelled
later.
I did submit an abstract for the "Data Engineering" track.
More talks are better!
I was looking at the submittal page, and the actual deadline is BEFORE May
23, not the day of May 23.
as well).
Comments?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
Suggest post this to users list too.
They mention mainframe data.
Maybe we can get someone (like from Google) to implement the P and V number
format characters, so that we have complete mainframe number support? I
think that's the last real COBOL-ish feature pending.
On Mon, May 16, 2022 at
I very much like the idea of pointing the VSCode debug environment at an
arbitrary TDML file, and seeing it put up a list of tests I can choose from
to debug.
Even if it only supports test cases where the schema, input data, and
expected infoset are all in external files (at least initially).
I have a few ideas here.
I suggest work toward "next release" should happen on 'main'.
Only if needed (such as a security issue), AND there is no easy near term
new release available on the 'main' branch then we create a maintenance
branch for the prior official release. But I would do this
https://www.i-programmer.info/news/197-data-mining/15355-apache-daffodil-gets-vs-code-extension.html
VScode debugger would help the most?
> With the issue of left over data, we do get an infoset. If we could
> visually overlay that over the actual data in the debugger it would
> probably make it very clear where things start going wrong focus the
> user to the right part of the schema.
>
&
="unsignedint8"/>
>
>
>
>
>
>
>
> *
&
Please comment on this idea.
The problem is that users write a schema, get "left over data" when they
test it. The schema works. The schema is, as far as DFDL and Daffodil is
concerned, correct. It just doesn't express what you intended it to
express. It IS a correct schema, just not for your
on releases, on what license
things must have, or on what other software components can be required,
etc. A good example of this is the IBM DFDL cross-testing rig, which
depends on IBM DFDL, which is closed source and licensed.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup
Congratulations to all the developers who worked on the Daffodil VS Code
capability. This is a huge step in the right direction for us!
DFDL Workgroup has already requested me to demo it Thursday on
our semi-weekly call, so I will do a little bit of edifact debugging with
it.
There is a
My wisecrack about never upgrading to Scala 3 is really just a wisecrack.
I'm sure we'll eventually migrate because libraries we use will, and
because we'll eventually want the features ourselves to improve the code
base.
Also, new developers learning Scala will want to learn the latest flavor
+1 binding
I did some breakpoint debugging of EDIFACT, and it worked to stop in
breakpoints anywhere in the schema, showing the schema element, infoset so
far, delta in infoset from prior step and showing position in the hex dump.
(I had the most trouble just getting all that fitting on the
A specific question: what about class to base-class relationships? Can a
base-class or java interface be in a separate jar/module?
On Thu, Mar 31, 2022 at 12:57 PM Mike Beckerle wrote:
> Taking this thread over to our dev list.
>
> Please sanity check this notion on how to re
; Sorry for the lengthy mail, it all may seem a bit strange, but the concept
> is around for years and it really helps with modular programming. Just as
> an exercise, check the MANIFEST.MF of some of your favorite open-source
> JARs, most in fact are built as bundles, and have Import-
/Manage-DFDL-Processors.html
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
overwhelming at first - you can't possibly participate in everything you'd
like. You have to pick some things, and be satisfied with that,
They are also rather amazing, and I expect you will find that attending is
well worth the time and expense.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF
st the vscode repo?
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On 2022/03/24 15:05:27 Shane Dell wrote:
> > >>>>>>>>>> So I think the log4j errors you are seeing are com
unsignedInt and avoid conversion error due to leading whitespace(s).
>
>
>
> Attila
>
>
> PS: if you can't see embedded image above, see attached PDF.
>
>
> On Wed, Mar 16, 2022 at 12:21 PM Mike Beckerle
> wrote:
>
>> Ok, I found the attachme
features
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
h" % "sbt-pgp" % "1.1.1")
// addDependencyTreePlugin
On Thu, Mar 24, 2022 at 12:39 PM Steve Lawrence
wrote:
> I'm on 1.6.2. Can you confirm you added the plugin to
>
>~/.sbt/1.0/plugins/plugins.sbt
>
> That error sounds like something you'd get if the
ess they changed
> something about this option in the newer 4.0.0 version?
>
> On 3/24/22 11:00 AM, Mike Beckerle wrote:
> > Either way build.sbt or other, I just get
> >
> > dependencyCheckAssemblyAnalyzerEnabled := Some(false)
> > ^
> > [error] Type error in expressio
Either way build.sbt or other, I just get
dependencyCheckAssemblyAnalyzerEnabled := Some(false)
^
[error] Type error in expression
On Thu, Mar 24, 2022 at 10:58 AM Mike Beckerle wrote:
> is "Somez" a typo?
>
> Does it matter that this is in build.sbt vs. global.sbt or any
always gets done.
>
> As to the error, I don't remember doing this, but also added this to
> ~/.sbt/1.0/build.sbt to disable the .NET analyzer:
>
>dependencyCheckAssemblyAnalyzerEnabled := Somez(false)
>
>
> On 3/24/22 10:45 AM, Mike Beckerle wrote:
> > We sh
We should add this sbt dependency check instruction to the release workflow
- which actually needs a section with a checklist of things to check/verify
like this. Or maybe it's a separate page, release-testing/verification.
However, I tried it (using version 4.0.0 of the plugin) on daffodil and
Since we have to fix the CVE issues, we should also update to Daffodil 3.3.0
On Thu, Mar 24, 2022 at 9:04 AM Steve Lawrence wrote:
> I think I've sort of found the issue with the different .class files. If
> I disassemble the class files that don't match, they all have diffs that
> look like
schema files.
Are there draft pages about this vscode debugger release on the daffodil
site?
On Fri, Mar 18, 2022 at 3:35 PM Mike Beckerle wrote:
>
> Since this vote closes sunday, and I won't have further test time before
> then, I have to vote now.
>
> Voting -1
>
> I couldn'
://issues.apache.org/jira/browse/DAFFODIL-2618 as a
> "not a bug" and I concur.
>
> I've looked at the other issues; should
> https://issues.apache.org/jira/browse/DAFFODIL-2664 fall into the "not a
> bug" category since it didn't require a change to Daffodil?
&
using RSA key 4B6A956D3ED3650268802E37274B8F1413A680AF
gpg: Good signature from "Michael J. Beckerle (Code Signing Key) <
mbecke...@apache.org>" [ultimate]
No warning.
So there is something different about the way my code signing key was
established.
Mike Beckerle
Apache Daffodil PMC | daffodil.
+1
I ran tests of 60+ regression test schemas which passed. I also tested
against a few very new schemas that are large and quite complex and
they passed.
I reviewed the release notes.
I downloaded all the artifacts and verified the signatures (after
remembering to import John I's public gpg
Since this vote closes sunday, and I won't have further test time before
then, I have to vote now.
Voting -1
I couldn't get the convenience binary .vsix file to work to debug EDIFACT
with a breakpoint in the 2nd file of the schema.
I went so far as to uninstall the older extension, shut down
%"test",
> > ---
> > )
> >
> > So it seems to be a Daffodil error, since this doesn't happen with
> > 3.0.0, but it does happen with 3.2.1
> >
> > Note: I'm running sbt 1.5.7 (Ubuntu Java 11.0.14), but I believe Mike
> > tried several dif
HOT"
> %"test",
> ---
> )
>
> So it seems to be a Daffodil error, since this doesn't happen with
> 3.0.0, but it does happen with 3.2.1
>
> Note: I'm running sbt 1.5.7 (Ubuntu Java 11.0.14), but I believe Mike
> tried several different versions when we first ran
I tried many things, including clean git clones of all related repos. This
problem is a very bizarre interaction.
The fact that the tests ran flawlessly under intelliJ IDEA, but failed
running sbt from the command line
I searched for sbt bugs related to exportJars. I did find
gt;> I know you're preparing to release 3.3.0.
>>
>> When do think this issue might be resolved? Which point release are you
>> targeting?
>>
>> On a related subject, Daffodil implements a subset of XPATH function.
>> Might dev-team consider implementin
d the rc soon (I won't have time to prepare a rc until Thursday
> evening and it's my first time so it would take more time).
>
> John
>
> -----Original Message-
> From: Mike Beckerle
> Sent: Tuesday, March 15, 2022 1:59 PM
> To: dev@daffodil.apache.org
> Subject:
Owl has a DFDL schema for a moderate size subset of the VMF data standard.
It takes well over a minute to compile it to a saved binary file. This on a
fast PC with 64Gigs of RAM.
This is really excessive. Something has to be going wrong algorithmically.
I think this is not enough to hold up the
Created https://issues.apache.org/jira/browse/DAFFODIL-2676
On Wed, Mar 16, 2022 at 12:21 PM Mike Beckerle wrote:
> Ok, I found the attachment. Sorry for the delay.
>
> The challenge here is you are thinking the
> xs:unsignedInt(../Line1.02-Satellite) call will tolerate white
Attila Horvath
wrote:
> Attachment can be found on
> https://lists.apache.org/list.html?us...@daffodil.apache.org list.
> Not sure why it didn't show up on dev - I sent msg to both lists.
>
> On Tue, Mar 15, 2022 at 3:41 PM Mike Beckerle
> wrote:
>
> > No attached PD
No attached PDF.
Removal of blanks from a number would normally be by way of DFDL "padding"
and "trimming" properties.
You need dfdl:textNumberJustification property, also textTrimKind,
textPadKind, textNumberPadCharacter.
You can also use textNumberPattern to indicate that a number may have
Ok, all the critical issues for 3.3.0 are fixed now.
Any volunteers for release manager?
On Mon, Mar 14, 2022 at 7:24 PM Mike Beckerle wrote:
> This was an easy fix.
>
> Once this gets merged I believe we have direction to move forward with
> 3.3.0 release process.
>
&
This was an easy fix.
Once this gets merged I believe we have direction to move forward with
3.3.0 release process.
Who would like to be release manager?
On Mon, Mar 14, 2022 at 6:06 PM Mike Beckerle wrote:
> So the 3 blocking issues have been fixed/merged.
>
> However, of several b
> -Original Message-----
> > From: Mike Beckerle
> > Sent: Wednesday, March 9, 2022 6:00 PM
> > To: dev@daffodil.apache.org
> > Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
> >
> > Once the revert/fix for regressions is merged, I think we're down
Anyone mind if I push a long, highly-visible, tag
"Start-Apache-Daffodil-VSCode" to the daffodil-vscode repo at this
commit: 793e7e7e2cb4a303d6be865922dfb80afbca46bc
(last commit before our team, from a microsoft contributor)
This is just to make it easier when visualizing the history in tools
g is preferable to these regressions.
>
> This will get us closer to a releasable 3.3.0.
>
>
>
>
>
> On Wed, Mar 2, 2022 at 2:12 PM Mike Beckerle wrote:
>
>> I've marked all the alignment/cyclic-deadlock regressions as blockers for
>> 3.3.0 along with the "
closer to a releasable 3.3.0.
On Wed, Mar 2, 2022 at 2:12 PM Mike Beckerle wrote:
> I've marked all the alignment/cyclic-deadlock regressions as blockers for
> 3.3.0 along with the "hammer" to
> just turn off alignment.
>
> The fixing suggested in the thread here may b
A quick search shows we have a handful of final case classes, but most are
not so marked.
I think this makes sense as a coding standard. I am not always strict about
this, but I tend to believe if you are deriving from a class it usually
should be abstract, not concrete, and case classes are
c & linux)
> >
> %USERPROFILE%\.vscode\extensions\asf.apache-daffodil-vscode-1.0.0\server\core\target\universal\daffodil-debugger-3.2.1-1.0.0.zip
> (windows)
> >
> >
> > On 2022/03/03 18:38:56 Mike Beckerle wrote:
> > > Hmmm. Ticket https://github.com/apache/da
Hmmm. Ticket https://github.com/apache/daffodil-vscode/issues/66 is closed,
so I expected breakpoints in different files of a multi-file schema should
work so long as they're all part of the same schema project/tree, i.e., not
in jar/classpath schemas.
I opened up the EDIFACT DFDL schema project
mplementing one or both of these options as tunables might help
> improve the alignment issue and would be reasonable to get in 3.3.0.
>
>
> On 2/23/22 11:08 AM, Mike Beckerle wrote:
> > So, we seem to be seeing a lot of regressions in various DFDL schemas
> like
> > most
I'm good with cut a release and iterate on testing that.
On Fri, Feb 25, 2022 at 11:03 AM Adam Rosien wrote:
> I think it's better to cut a release and iterate on that testing-wise.
>
> On Wed, Feb 23, 2022 at 7:24 AM Mike Beckerle
> wrote:
>
>> I have not had time to tes
tps://cwiki.apache.org/confluence/display/DAFFODIL/Roadmap+for+Upcoming+Releases)
> change as a result of 3.3.0 being released asap?
>
> John
>
> -Original Message-
> From: Mike Beckerle
> Sent: Tuesday, February 22, 2022 10:44 AM
> To: dev@daffodil.apache.org
> S
I have not had time to test the vscode debugger recently.
We could hold off doing that, or I could do that as part of the rc1
evaluation process if you prefer before we vote on accepting it.
On Tue, Feb 22, 2022 at 3:06 PM John Wass wrote:
> All issues are resolved. If we are good to
One issue, which may be in the NITF schema, or may be a daffodil issue is
reported on NITF here:
https://github.com/DFDLSchemas/NITF/issues/15
On Tue, Feb 22, 2022 at 10:43 AM Mike Beckerle wrote:
> A number of people are asking for 3.3.0, with its many bug fixes, to be
> release
A number of people are asking for 3.3.0, with its many bug fixes, to be
released asap.
Are there any remaining issues that must be fixed before this release?
Otherwise I'd like to suggest we release 3.3.0.
Where should we put the additional VSCode DFDL Intellisense editing
capability?
It's not integrated into the VSCode debugger at this time, though they may
get combined some day in the future. Arguably, some people may want the
editing without the debugging, but the opposite is a lot less likely.
Path.of thing is a java JVM version thing. I think it is not in Java 8.
Introduced after.
On Wed, Jan 19, 2022 at 2:11 PM GitBox wrote:
>
> stevedlawrence commented on pull request #73:
> URL:
> https://github.com/apache/daffodil-vscode/pull/73#issuecomment-1016782648
>
>
>I don't think
The scala-xml library looks to be adding namespace awareness.
This is a significant change for us. When this comes up in a scala steward
update, we'll have to watch carefully.
The lack of this support was a shortcoming of scala's XML support from the
start.
-- Forwarded message
A recent suggestion I have taken to heart, is to annually remind the PMC
and all dev list participants, to review
https://www.apache.org/theapacheway/
Since security of software has been a hot topic of late (since the Log4J
CVEs in December) it is worth thinking about how ASF emphasis on
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
required code changes, so I don't think
> there is a workaround aside from downgrading Scala to 2.12.11.
>
> Also, this fix was part of Daffodil 3.1.0, so any previous Daffodil
> versions probably shouldn't use a Scala version newer than 2.12.11, at
> least if there are plans t
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
Does the CLI have a way to use DFDL schemas where all of them are
specified in jar files on the classpath?
I know all but the primary one can be on the classpath, but what if
all of them are packaged in jars, none are textual in files.
The Apache Daffodil community is pleased to announce the release of
version 3.2.1
This is an important patch release which supersedes the recent 3.2.0 release.
All users should upgrade from 3.2.0 to 3.2.1 immediately, as it
contains two important things:
* Log4J dependency updated to 2.17.0 to
out error.
> - Executed the nightly performance test suite on supported Java versions 8
> and 17 without error.
> - Executed dfdl-schema repo sub-module SBT test suite on supported Java
> versions 8 and 17 without errors .
>
> -Original Message-
> From: Mike Beckerle
> S
201 - 300 of 544 matches
Mail list logo
