[
https://issues.apache.org/jira/browse/SOLR-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423149#comment-17423149
]
Dawid Weiss commented on SOLR-15670:
------------------------------------
bq. Adding an opt-in option to skip all ref-guide gradle tasks would make it a
lot easier for custom build systems to skip these steps when the resulting
artifacts are never used.
I am a bit reluctant to add such options. They repeat what's already in gradle.
I think those custom builds should be more specific about what they need and
issue correctly scoped project builds, for example:
{code}
gradlew -p solr/packaging assemble --console=plain
{code}
doesn't touch the ref guide at all, doesn't require magic and should be in fact
faster than disabled tasks (that are still part of the execution graph).
If you're using something frequently, add a shell alias that builds it - much
like you'd have to do with a custom property. Can you give me an example when
the above would be insufficient?
> Introduce Gradle parameter to skip ref-guide tasks
> --------------------------------------------------
>
> Key: SOLR-15670
> URL: https://issues.apache.org/jira/browse/SOLR-15670
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Gradle
> Affects Versions: main (9.0)
> Reporter: Houston Putman
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> A lot of users have no need of building a local reference guide when
> compiling and building artifacts.
> Adding an opt-in option to skip all ref-guide gradle tasks would make it a
> lot easier for custom build systems to skip these steps when the resulting
> artifacts are never used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
