I'd also like to upvote DAFFODIL-2596, because we're simply running into it a great deal now, and it is quite confusing especially to new DFDL schema writers.
On Wed, Dec 14, 2022 at 6:07 PM Mike Beckerle <[email protected]> wrote: > I'd vote to increase priority of > https://issues.apache.org/jira/browse/DAFFODIL-2683 which is blocking > integration of Daffodil into Apache Kafka. This is the bug about OSGI (and > Java 9 Modules) compatibility. > > It is also important for anyone who is trying to use some sort of > modularization to cope with the rather enormous number of dependencies > Daffodil drags in. > > Fixing this is a scripting exercise to introduce package dirs, and fix up > all corresponding imports so that no package has contributions from more > than one jar/module of Daffodil. > > > On Fri, Dec 9, 2022 at 12:11 PM Interrante, John A (GE Research, US) < > [email protected]> wrote: > >> I want to save time not having to point out or fix formatting issues >> during pull request reviews (I've had to spend time doing both). I would >> like someone to obtain a scalafmt configuration for the standard Scala code >> style, provide guidance how to configure IDE's that do autoformatting to >> use that configuration, and make sbt run scalafmt on the codebase >> automatically during a build. Shall we prioritize >> https://issues.apache.org/jira/browse/DAFFODIL-2133? >> >> I don't know if we should prioritize >> https://issues.apache.org/jira/browse/DAFFODIL-2152 (has anyone said >> they need to use Daffodil with Scala 2.13/3.x yet?), but in general I don't >> like seeing a lot of easily fixed IDE warnings when viewing Daffodil source >> files in IDEA. Some of these warnings are about things like return types >> for public methods that will be needed to fixed to upgrade to Scala >> 2.13/3.x later anyway. >> >> I also would like to prioritize >> https://issues.apache.org/jira/browse/DAFFODIL-2536 (refactoring for >> separable runtimes/back-ends). I would prefer Steve or Mike do that >> refactoring since they know the code better than anyone else but I can >> weigh in with input from writing the C back-end and take on some delegated >> work. >> >> A teammate wants to know how to run Daffodil in streaming mode within a >> Docker container (reading from a TCP socket, writing to another TCP >> socket), so it would be good to update the streaming documentation too ( >> https://issues.apache.org/jira/browse/DAFFODIL-2718). >> >> That's all I found within the first 200 "major" issues. >> >> John >> >> -----Original Message----- >> From: Mike Beckerle <[email protected]> >> Sent: Tuesday, December 6, 2022 7:11 PM >> To: [email protected]; [email protected] >> Subject: EXT: What bug to fix? - Bug scrub for Daffodil 3.5.0 (and beyond) >> >> Our next release will be 3.5.0 and our convention is that odd numbered >> releases are focused on bug fixing. >> >> That raises the question: which bugs should we fix? >> >> We have 468 unresolved tickets which is enough that properly prioritizing >> and labeling them is hard simply due to volume. >> (Here is the list of them: >> https://issues.apache.org/jira/projects/DAFFODIL) >> >> So I'd like to ask our dev/user communities to up-vote and/or comment on >> our JIRA tickets from their perspective. >> >> Alas.... logistics.... Apache JIRA requires accounts now (due to the >> darned spammers). So.... If you do not have an Apache JIRA account you >> won't be able to up-vote or comment on tickets. >> But... I can create one for you allowing for you to upvote/comment >> tickets. >> Just send me, (personally - do not hit reply or reply all), your >> preferred userid, full name, and email. Note: If you have a github account >> then that userid is a good choice. >> >> Note that bugs can include performance problems as well as things not >> working as they should. Some kinds of missing features can even be >> considered to be "bugs" even if our JIRA classifies them as improvements or >> new features. >> >> Thanks >> >> 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 >> >
