Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/15553
@srowen This is explicitly supports maven.test.skip=true - the rationale
for using it can be project specific (generating clean builds for various
profile combinations, internal release builds from an apache tagged released
version, etc for example).
We are seeing close to halving the build time for clean builds (use of
zinc, batched build, etc is already enabled).
Regarding complexity of the build - if there are any suggestions on how to
reduce that, please do let me know. The pr primarily reorganizes all test scope
dependencies into a profile of its own which is activated by default unless
maven.test.skip=true; which seems to be the only recommended way to do it from
maven docs/discussions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
