From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

is there a good way to build an application jar in one "module" and then pull it into another but not on the classpath? I need to stand it up as a server for tests.

Define a custom `dependencyScope` configuration on which you define the dependency and a custom `resolvable` configuration extending from it, then use the resolution result of that configuration to get the jar and use it however you like

got a "how to" link for how to do that? since I've not done it before

See <https://docs.gradle.org/current/userguide/declaring_dependencies.html#sec:resolvable-consumable-configs>
Gradle 8.4 added factory methods (still incubating) `dependencyScope` and `resolvable` to help create those: <https://docs.gradle.org/8.4/release-notes.html#configuration-role>

```val server = configurations.dependencyScope("server")
val serverClasspath = configurations.resolvable("serverClasspath") {
  extendsFrom(server.get())
  // add attributes here for variant selection if needed
}
dependencies {
  server("…")
}
tasks {
  register&lt;JavaExec&gt;("runServer") {
    classpath = serverClasspath.get()
    mainClass = "…"
  }
}```

:point_up:
And if on an older Gradle version or don't want to use incubating just create the configurations the classical way.

One slight variation, `val server by` instead of `val server =`, then you can save the `.get()`, as configurations are not treated lazily anyway.

Oh, TIL you can `by` such providers. Will refactor a few build scripts, thanks! :wink:

iirc you can `by` all providers to `.get()` them.

Just in most situations you don't want or need an additional variable where you could use `by` but just `get` the original variable. But in some situations like here it is quite handy :slightly_smiling_face: