Thanks. That workaround is great. It seems that in mixed scala/java modules, scaladoc is used by sbt, and it fails on java enum types. This seems to be a known bug (though the ticket is closed!) the workaround is to separate java sources into their own module so that sbt will run javadoc instead.
________________________________ From: Steve Lawrence <[email protected]> Sent: Wednesday, October 9, 2019 2:45 PM To: [email protected] <[email protected]> Subject: Re: sbt scaladoc tool failing on java codegen files Looks like publishing has a dependency on building/publishing the docs. Since that's expected to fail right now, you can add this to the runtime2 project to disable publishing the docs: .settings(publishArtifact in (Compile, packageDoc) := false) On 10/9/19 2:28 PM, Beckerle, Mike wrote: > > On my PR branch https://github.com/apache/incubator-daffodil/pull/274 > > I am struggling because I can't get sbt publishLocal to create a published > jar for the new runtime2 module. > > I think I have modified build.sbt to make runtime2 appear everyplace runtime1 > appears. It certainly compiles and runs tests fine. > > One problem is that building the documentation fails on some of the java code > in daffodil-runtime2 from Julian's codegen library. Two files have "type > errors" that are clearly just issues with the scaladoc tool it seems. The > files comple fine, but get type errors that are spurious during publishLocal. > > This may be what is preventing the daffodil-runtime2 jar from publishing. > > Any suggestions on how to fix/work-around welcome. > > >
