[
https://issues.apache.org/jira/browse/SOLR-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423996#comment-17423996
]
Houston Putman commented on SOLR-15670:
---------------------------------------
I think it is easier on the build side, but when trying to run {{gradle check}}
without the ref guide options gets a little trickier, since there many tasks
across the project that we want to run, and we have to list out the multiple
ref-guide checks that we want to exclude. (The two explicit tasks aren't hard
to hide, but there are hidden ones that come from the plugins)
Ideally this wouldn't be an issue, since the rest of the project can run behind
corporate walls fairly well. However the ruby gradle plugin in particular
cannot handle private gem repos (e.g. artifactory), which makes building this
part very very difficult.
[~dweiss] do you have a suggestion for the doing {{gradle check}} part without
the ref-guide tasks?
> 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
