mocobeta commented on code in PR #811: URL: https://github.com/apache/lucene/pull/811#discussion_r850334643
########## help/workflow.txt: ########## @@ -25,11 +25,22 @@ Assemble a single module's JAR (here for lucene-core): gradlew -p lucene/core assemble ls lucene/core/build/libs +Assemble all JARs: +gradlew assemble + Create all distributable packages, POMs, etc. and create a local maven repository for inspection: gradlew mavenLocal ls -R build/maven-local/ +Assemble Javdocs on a module: Review Comment: > Separately - do you ever assemble javadocs for a single module? What's the point of doing that? Yes, sometimes - to see the changes on javadocs are fine in HTML (and it is convenient for lining in my usage). I added this line mainly for developers who want to contribute documentation. -- 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: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
