olabusayoT commented on code in PR #1479:
URL: https://github.com/apache/daffodil/pull/1479#discussion_r2070737958
##########
build.sbt:
##########
@@ -28,20 +28,13 @@ lazy val genTunablesDoc = taskKey[Seq[File]]("Generate
tunables doc from dafext.
lazy val daffodil = project
.in(file("."))
- .enablePlugins(JavaUnidocPlugin, ScalaUnidocPlugin)
+ .enablePlugins(ScalaUnidocPlugin)
.aggregate(
cli,
codeGenC,
- core,
- io,
- japi,
- lib,
Review Comment:
> value in creating a daffodil-charset and daffodil-layer directory/jar that
contains the interfaces for building custom layers and charsets, similar to
what we have with daffodil-udf? Or maybe we have a daffodil-plugins that
contains all the udf, layer, and charset interfaces? Or do we want to merge
daffodil-udf into daffodil-core so no matter what you're doing, you just depend
on daffodil-core? I have no strong preference for either approach, but it seems
a inconsistent to have udf be it's own jar and other plugins be part of
daffodil-core.
Created DAFFODIL-2994
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@daffodil.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
