fix: improve the javadoc generation#642
Conversation
7c32998 to
ea78d5c
Compare
examples/substrait-spark/src/main/java/io/substrait/examples/util/SubstraitStringify.java
Show resolved
Hide resolved
examples/substrait-spark/src/main/java/io/substrait/examples/util/SubstraitStringify.java
Outdated
Show resolved
Hide resolved
aa66f53 to
3c5cf68
Compare
3c5cf68 to
fdb782a
Compare
11c6fa5 to
13b4ed9
Compare
bd4e0e9 to
d66c27e
Compare
|
@nielspardon @andrew-coleman @benbellick @bestbeforetoday @vbarua I've updated the merge conflicts; if there aren't any more urgent comments on this one... would it be ok to merge please? Help ro reduce any conflicts with other JavaDoc changes. Also this one helps to reduce the overall 'noise' level from the generated protobuf's javadoc. Thanks |
Make all components put javadoc into a consistent root. This achieves the following - means the javadoc for the generated protobuf can be kept quiet - as we can't adjust the javadoc here - there is a single place for javadoc that could be published - the isthmus and core and protobuf projects can be interlinked - isthmus can be linked with the calcite javadoc - overview pages can be added - all under a versioned directory for easy maintence To date there isn't (AFAIK) a stightforward maintainable way to merge javadoc form multi-component projects Signed-off-by: MBWhite <whitemat@uk.ibm.com>
Signed-off-by: MBWhite <whitemat@uk.ibm.com>
Signed-off-by: MBWhite <whitemat@uk.ibm.com>
Signed-off-by: MBWhite <whitemat@uk.ibm.com>
Signed-off-by: MBWhite <whitemat@uk.ibm.com>
Signed-off-by: MBWhite <whitemat@uk.ibm.com>
Signed-off-by: MBWhite <whitemat@uk.ibm.com>
c7b5824 to
5abcd50
Compare
Signed-off-by: MBWhite <whitemat@uk.ibm.com>
5abcd50 to
776b5d8
Compare
| tasks.named<Jar>("javadocJar") { | ||
| val shared = rootProject.layout.buildDirectory.dir("docs/${version}").get().asFile | ||
| if (!shared.exists()) { | ||
| println("Creating a dir for javadoc ${rootProject.buildDir}/docs/${version}") |
There was a problem hiding this comment.
I've seen a deprecation warning for the usebuildDir when I ran this locally. seems one should use layout.buildDirectory.get() instead.
| tasks.named<Jar>("javadocJar") { | ||
| val shared = rootProject.layout.buildDirectory.dir("docs/${version}").get().asFile | ||
| if (!shared.exists()) { | ||
| println("Creating a dir for javadoc ${rootProject.buildDir}/${version}") |
There was a problem hiding this comment.
I've seen a deprecation warning for the usebuildDir when I ran this locally. seems one should use layout.buildDirectory.get() instead.
|
|
||
| // Only the generated proto sources | ||
| setSource(fileTree(protoJavaDir) { include("**/*.java") }) | ||
| // source(fileTree(immuteableJavaDir) { include("**/*.java") }) |
There was a problem hiding this comment.
I guess this line is not really needed
| // source(fileTree(immuteableJavaDir) { include("**/*.java") }) |
|
|
||
| // Only the generated proto sources | ||
| setSource(fileTree(immuteableJavaDir) { include("**/*.java") }) | ||
| // source(fileTree(immuteableJavaDir) { include("**/*.java") }) |
There was a problem hiding this comment.
| // source(fileTree(immuteableJavaDir) { include("**/*.java") }) |
Make all components put javadoc into a consistent root. This achieves the following
To date there isn't (AFAIK) a stightforward maintainable way to merge javadoc form multi-component projects