[
https://issues.apache.org/jira/browse/SOLR-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424538#comment-17424538
]
Houston Putman commented on SOLR-15670:
---------------------------------------
Yeah, I hit the verifyLocks issue that you saw.
Also we are disabling the tasks ourselves by injecting some gradle code, which
used to work very well. I'm perfectly fine not adding something in solr to
solve this, if no one else would stand to benefit. But I would really like to
nail down why these dependencies are downloaded even though the tasks are
skipped.
I've determined that using the following snippet works when using
{{'com.github.jruby-gradle.base' version '2.0.0'}} but not when using
{{'com.github.jruby-gradle.base' version '2.0.1'}}. (Code is purely for testing
purposes) I'll try to see why the new jruby-gradle version doesn't play well
with dependencies.
{code:java}
afterEvaluate {
project.tasks.each {
it.enabled = false
}
}
{code}
> 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
> Attachments: SOLR-15670.patch, SOLR-15670.patch
>
> 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
