Skip to content

Conversation

@dsmiley
Copy link
Contributor

@dsmiley dsmiley commented Oct 27, 2025

This introduces a convenient way to start Solr from Gradle, which I think is thus the most convenient way to start Solr period. It relies on devSlim. Note that IntelliJ can run Gradle tasks (action "Execute Gradle Task"), which in turn makes debugging simple, as you just need to hit the debug symbol.

Downsides / trade-offs:

  • skips bin/solr (bash), thus isn't in sync with obscure settings it sets. Not going to address that at all; since being a "JavaExec" task is quite the point, and is what benefits from being able to debug quickly.

@dsmiley dsmiley requested review from epugh and janhoy October 27, 2025 17:44
@github-actions github-actions bot added documentation Improvements or additions to documentation tool:build labels Oct 27, 2025
Copy link
Contributor

@epugh epugh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm. Thanks for the docs

println "To attach a debugger, at the CLI pass: --debug-jvm"
println "To pass JVM args, at the CLI pass: -PjvmArgs='--add-modules jdk.incubator.vector'"
println "To pass system properties, at the CLI pass: -Djetty.port=8983"
println "To pass system properties, at the CLI pass: -Dsolr.port.listen=8983"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

gradlew -p solr/packaging dev
ls solr/packaging/build/dev # expanded directory
Build & run Solr directly from Gradle, skipping "bin/solr", retaining data between runs:
gradlew -p solr/packaging runDevSlim
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a runDev to match?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like there to be one for ease of remembering it. But I want the slim thing to be the default, not "full". I could just rename this to "runDev" and stop there. Later we can decide if we want to bother with offering a full as well. WDYT?

IMO "dev" should also just be an alias to "devSlim". If you want full, call devFull. I disagree with "dev" building both. WDYT @HoustonPutman ? (I recall you introduced this in 2023).

And for another aside... the name "dev" is not something I would have chosen... I think it was Dawid Weiss who thought of something quickly and there wasn't feedback at the time.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, I think we could always rename it..

@dsmiley
Copy link
Contributor Author

dsmiley commented Nov 6, 2025

It's now runDev (still uses the devSlim), and I'll merge this tomorrow.

@dsmiley dsmiley changed the title New runDevSlim alternative to "dev" New runDev alternative to "dev" Nov 7, 2025
@dsmiley dsmiley merged commit d6c8095 into apache:main Nov 7, 2025
5 of 6 checks passed
@dsmiley dsmiley deleted the runDevSlim branch November 7, 2025 22:40
dsmiley added a commit that referenced this pull request Nov 9, 2025
dsmiley added a commit that referenced this pull request Nov 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation tool:build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants