WTF DOES AN OPEN SOURCE FOUNDATION DO?! Tomorrow I'm interviewing one of the board members of the Apache Software Foundation to discuss exactly that. https://lu.ma/01lv9yy0 You'll learn about what these foundations do, how they work, how developers and founders can best engage with them, and so much more. Hope to see you there Gradle Friends, this will be a good one! 🙂

New Understanding Gradle video: #21 Test and Code Coverage Reporting

Hello everyone, - We are excited to announce our first Developer Productivity Engineering Summit! The event will take place in San Francisco on November 2-3, 2022. In this two-day summit we’ll focus exclusively on Developer Productivity Engineering, featuring speakers from Airbnb, DoorDash, Google, Gradle, LinkedIn, Microsoft, Netflix, Slack, Square, and Uber. Check out the event details at the DPE Summit website << dpesummit.com>>. Use the code gc-slack-100 to receive a $100 discount off the registration price. See you there!

Hello everyone. Understanding Gradle videos made by @Jendrik Johannes are useful for new beginner. So I am going to translate these videos into Chinese and put them on Bilibili, here are two videos: 1. The Settings File: https://www.bilibili.com/video/BV1Bd4y1R77A?spm_id_from=333.999.0.0&amp;vd_source=c59ed3775ab99dca21a64247a2b2a255 2. The Build File: https://www.bilibili.com/video/BV1iG4y167e3?spm_id_from=333.999.0.0

Hello everyone, - just another DPE Summit related announcement it is 🙂 We opened a new channel for updating the community about our event. Go check the #dpe-summit channel --> <https://gradle-community.slack.com/archives/C04063WRPT4 >>

If you're using GitHub Actions for your Gradle builds (and not yet using

gradle/gradle-build-action

) you may want to take a look at this short blog post: A Better Way to Use Gradle With Github Actions

We are working on the September Gradle Build Tool newsletter, please let me know if you know of interesting news worth covering!

There are two new Understanding Gradle videos (since I posted here last time): • The JavaCompile Task (How does Gradle select and call the Java compiler and what are the different options?) - • Caching (What are the caching mechanisms Gradle uses? Where, and why, to configure them?) -

This message was deleted.

👌 looks very nice 🙂 I think someone asked you somewhere already, have you thought about measuring memory usage of processes spawned by Gradle? I tried a PoC a while back and it should be possible to modify jvmargs of each

JavaExec

task to attach an agent that would measure that process available memory and memory usage

We are working on the October Gradle Build Tool newsletter, please let me know if you know of interesting news worth covering!

Hi, folks! I have just published the Gradle Changelog Plugin v2.0.0 This is a plugin providing tasks and helper methods to simplify working with a changelog that is managed in the keep a changelog style. If you maintain th If you maintain the project changelog in Markdown file, this is something that may be useful for you. 🙂 Release note: https://github.com/JetBrains/gradle-changelog-plugin/releases/tag/v2.0.0

We have published a brand new training for Gradle Build Tool! This is designed for JVM-based developers that have used Gradle and are looking for best practices and some deeper understanding. Some highlights are testing suites and toolchains. Free to all, build your JVM tooling knowledge base! Nov 17th

Released 1.0 of the java-ecosystem-capabilities plugin in the gradlex.org namespace. It enhances metadata of widely used components (javax*, Guava, asm, ...) to detect conflicts and avoid duplications on the classpath. I initially released an experimental version of this plugin some months ago. Thanks for all the feedback from the community (@Thomas Broyer, @Vladimir Sitnikov, @Vampire and everyone else) which motivated me to put more work into it. Thanks @benedikt for helping/convincing me to call this 1.0 and maybe drive this further. I always said someone should do something like this and now... well we have something 🙂. I am happy about more feedback/contributions/ideas. The idea (at least my idea) was to have some place where we - the Gradle community - collect the metadata about OOS components that should be on Maven Central (but isn't - since most projects publish with Maven ans have not Gradle Metadata) to all have a bit less of a dependency hell in all our projects. https://github.com/gradlex-org/java-ecosystem-capabilities

When it comes to modularization, Gradle builds on top of what Java supports and provides. I often see confusion about where the functionality of Java tools (

javac

/

java

) end and where Gradle starts. That's why I'll do a couple of videos to explore this step-by-step. Here is the first one, in which I talk about Java's Classpath concept:

Hi, everyone. I am a new member 👀

Hi to all,.... Kind regards to all of you.

Inspired by https://old.reddit.com/r/java/comments/z7q4ha/a_poem_about_java_written_by_textdavinci003_gpt3/, I asked the AI to generate a poem about the differences between Maven and Gradle:

Maven and Gradle are two build tools,
That find the dependencies to use,
Maven is a powerhouse,
While Gradle is less obtuse,

Maven's strength is in its conventions,
It's a standard tool to choose,
Gradle's scripts are more flexible,
And more freedom they will let you use,

Maven is an XML based system,
That can be a bit verbose,
Gradle uses Groovy,
Which is more concise,

Maven is good for Java,
But Gradle is much more,
It can do many languages,
And you can adjust the build score,

Maven is traditional and tried,
But Gradle is much more modern,
Maven is a bit more rigid,
But Gradle is more often chosen.

It is, I think, unfortunate that in a tweet about Gradle 8, the snippet used as an illustration has a couple of issues: https://twitter.com/gradle/status/1598429687625449472

Once you split your Java project into components, you can have multiple compile classpaths. You can leverage that to have neatly isolated components with "plain old Java" at development time. In my second video on Java Modularity, I talk about how this is set up with Gradle and why to distinguish between

implementation

and

api

scopes,

Gradle has published some design specs. Internally, we use design specifications to collaborate on new Gradle features. To make our development process more open and transparent, our design specifications are publicly available via a Google Drive folder. This is still a work-in-progress and new documents will be added over time. We welcome community members to take a look. You can comment and provide feedback on all documents still In-Progress. We plan to use these documents to help guide new community contributions. Feel free to link to these documents in GitHub or share them with others. To know when new docs are added we have the #design-specs channel that will list each new doc overt time.

We are working on the December Gradle Build Tool newsletter, please let me know if you know of interesting news worth covering!

Are you frustrated by the

javax

to

jakarta

package name change? We've been working on making the upgrade to Jakarta EE 9 and later easier with our jakartaee-migration plugin. This plugin was built internally while preparing for our Spring Boot 3 / Spring Framework 6 upgrade. We have a long tail of libraries using legacy

javax

APIs, and we'll need to roman-ride both API namespaces for some time. This plugin uses capabilities, capabilities resolution and artifact transforms to make the process of migrating to Jakarta EE less frustrating and error prone. As always, ideas, feedback and contributions for our plugins are welcome!

Here is my new video on Java Modularity with Gradle. Are there unused (or too much) Jars on your compile classpaths? Do you even know? Learn how to use the Dependency Analysis plugin by @tony to clean up your compile classpaths and keep them in shape.

We are working on the January Gradle Build Tool newsletter, please let me know if you know of interesting news worth covering!

Next Java Modularity video: The dependency resolution of Gradle helps to avoid conflicts on the classpath (which Java alone won't): ❓ When does a conflict occur? ❗ How/why can Gradle resolve it? 😕 How to find undetected conflicts? 💡 What to do about those? Featuring: • Classpath Collisions Detector plugin: https://github.com/REPLicated/classpath-collision-detector • Java Ecosystem Capabilities plugin: https://github.com/gradlex-org/java-ecosystem-capabilities

@tony wrote a follow up to his "Herding elephants" articles: https://developer.squareup.com/blog/stampeding-elephants/

Hey gang! Tomorrow morning as part of our open source community events, we are hosting a DORA metrics masterclass with one of the Google Cloud DORA wizards! Hope you can join us, it’ll be filled with practical insights on how to make DORA actionable! 🙂 https://merico-dev.zoom.us/webinar/register/WN_ho68QdLETgOLYgOnTWL1ww P.S. apologies if this is the wrong place/way to share this!

Hello! Feel like you need a Gradle Mentor? Apply here. This program is designed for beginner developers from underrepresented segments of the developer community. To get accepted you should have a Gradle project in mind and be able to devote time to learn and grow your Gradle skills. Read more about what this entails in this blog post or see who was accepted into cohort one last year.