lucene/help/workflow.txt
Dawid Weiss 5ab59f59ac SOLR-11207: minor changes:
- added 'owasp' task to the root project. This depends on
dependencyCheckAggregate which seems to be a better fit for multi-module
projects than dependencyCheckAnalyze (the difference is vague to me
from plugin's documentation).

- you can run the "gradlew owasp" task explicitly and it'll run the
validation without any flags.

- the owasp task is only added to check if validation.owasp property
is true. I think this should stay as the default on non-CI systems
(developer defaults) because it's a significant chunk of time it takes
to download and validate dependencies.

- I'm not sure *all* configurations should be included in the check...
perhaps we should only limit ourselves to actual runtime dependencies
 not build dependencies, solr-ref-guide, etc.
2020-01-26 10:45:05 +01:00

41 lines
1.0 KiB
Plaintext

Typical workflow and tasks
==========================
This shows some typical workflow gradle commands.
Run tests on a module:
gradlew -p lucene/core test
Run test of a single-class (run "gradlew :helpTests" for more):
gradlew -p lucene/core test --tests "*Demo*"
Run all tests and validation checks on a module:
gradlew -p lucene/core check
Run all tests and validation checks on everything:
gradlew check
Run all validation checks but skip all tests:
gradlew check -x test
Assemble a single module's JAR (here for lucene-core):
gradlew -p lucene/core assemble
ls lucene/core/build/libs
Create all distributable packages, POMs, etc. and create a
local maven repository for inspection:
gradlew mavenLocal
ls -R build/maven-local/
Put together Solr distribution:
gradlew -p solr/packaging assemble
ls solr/packaging/build/solr-*
Other validation and checks
===========================
Generate a report of dependencies with known OWASP vulnerabilities:
gradlew :dependencyCheckAnalyze
open ./build/reports/dependency-check-report.html