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

Gradle Community

let me break the ice with a probably stupid question: I always wondered why the backslash in `distributionUrl=https\://` in gradle/wrapper/gradle-wrapper.properties

<https://docs.oracle.com/javase/6/docs/api/java/util/Properties.html#load(java.io.Reader)>
&gt; The key contains all of the characters in the line starting with the first non-white space character and up to, but not including, the first unescaped `'='`, `':'`, or white space character other than a line terminator. All of these key termination characters may be included in the key by escaping them with a preceding backslash character; for example,
&gt; `\:\=` 

yeah, I never realized it either until I saw that escape inside the wrapper properties :slightly_smiling_face: especially for the `:`

So yeah, it is actually superfluous, just what the serializer by default adds.

<https://gradle-community.slack.com/archives/C06JG95HREY/p1725342869133759>

a question about developing, let's suppose you are on a feature branch and you need to modify a binary plugin for quickly prototype and colleagues have to try that as well
do you prefer to use a composite build or publish the plugin to a different gav/artifact in this case?

If publishing, I'd publish a snapshot version, not different coordinates.
Whether to do one or the other probably majorly depends on the case.

Would it be nice feature addition - gradle adds test fixture artifact to test configuration if dependency has test fixtures published?

Not so sure whether that makes sense.
You can not so easily determine whether test fixtures are published up-front.
And just that it publishes test fixtures does not necessarily mean that each consumer wants to use them. :man-shrugging:

As for me, the discovery mechanism is similar to documentation or source published. Sure it is mostly IDE who consumes it now.

But the IDE - i.e. the consumer - says "give me these variants if they exist and if not, don't bother"

Oke, agree. The explicit dependencies is always nicer implicit.

When Open Source Isn’t: How OpenRewrite Lost Its Way
<https://medium.com/@jonathan.leitschuh/when-open-source-isnt-how-openrewrite-lost-its-way-642053be287d|https://medium.com/@jonathan.leitschuh/when-open-source-isnt-how-openrewrite-lost-its-way-642053be287d>

Are you going to NixCon in September, <@U07RX5TRM9U>? <https://2025.nixcon.org/|https://2025.nixcon.org/>

No, I'm on vacation that week :white_frowning_face: