mastodon.top est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastodon.top est une instance francophone stable, régulièrement mise à jour et accessible à tous hébergée par VirtuBox

Statistiques du serveur :

1,4K
comptes actifs

#gradle

1 message1 participant0 message aujourd’hui

Dear Gradle, Why So Stubborn?
Do I do something wrong?

Watching juniors try to set up a project and being greeted by cryptic stack traces like it's some kind of initiation ritual.

`Unsupported class file major version 61`
`invalid CEN header zip64 no access package`, ...

Java can compile code for older versions just fine.
It's literally designed for that.
Oh why, must Gradle behave like a bitter librarian who refuses to hand over a book unless I whisper the exact Dewey Decimal Code?
Every other Language will laugh again at java, seeing this.

💡 Why is Gradle bound to a java version? And if Gradle knows it needs Java 11… why doesn't it just do this for me?
Like using `/usr/libexec/java_home -v 11` in background?

🤖 Is there a clean way to force Gradle into submission without adding another tool like SDKMAN or jabba or YunaBraska/gradle-java-fix or whatever the trendy painkiller of the week is?

#Java#Gradle#BuildTools

Hey there #fediverse, I’m looking to hire a senior engineer to work with some awesome folks on #Netflix’s build tools & test infrastructure. If you are interested please apply online! (see link in Toot)

My DMs are open if you have any questions about the role or if you want to let me know that you applied.

#Java #JVM #Gradle

explore.jobs.netflix.net/caree

explore.jobs.netflix.netSenior Software Engineer (L5) — Build & Dependency Management Team (JVM Ecosystem) | USA - Remote | NetflixCommon Languages and Tools: Java & other JVM languages, Gradle, Nebula, Spring Boot, JUnit, GraphQL, Kafka, PostgreSQL. Implement and manage build solutions that enhance the efficiency and reliability of software delivery. Develop and maintain backwards-compatible tools for dependency management and analysis. Integrate internal and vendor-provided build and test infrastructure into engineering workflows, focusing on reliability and ease of use. Design and develop tools and infrastructure to automatically detect, quarantine, and reproduce flaky tests. Create and maintain tools for analysis of distributed tracing tools for test runs. Develop and integrate software solutions that provide high-quality synthetic test data generated from captured production traffic and API schema registries. Correlate test coverage data with code changes, runtime execution, and trace data for comprehensive reporting. Maintain a strong focus on scalability, usability, and reliability in platform design to support a growing cohort of engineers. Be willing and able to showcase our team's offerings to internal audiences Consult with other teams about how to best collaborate, integrate, and/or set up solutions for their needs A skilled software engineer with experience in developer platform or productivity teams. A meticulous software designer who researches and documents technical tradeoffs clearly and concisely. A self-motivated and organized individual who can independently drive engineering-wide solutions. A proactive communicator who engages effectively with technical and non-technical stakeholders. An advocate for strong build, dependency management, and testing practices, with familiarity in popular build tools, test frameworks, code coverage tools, continuous integration systems, and post-deployment verification methods (a healthy contempt for flaky tests is a plus). You have shipped and maintained Java code in production. You have worked on various technology stacks and are familiar with a variety of ways that software could be designed for different optimizations. You have designed and implemented build and dependency management solutions. You have built (and tested) custom Gradle plugins. You have assembled JVM Spring Boot applications using Gradle. You have experience with Nebula, Gradle, Maven, etc, for dependency management. You have experience with using and explaining Develocity dashboards. You are comfortable working with Zipkin or similar tools in the tracing space. You have implemented advanced log, metric, or error stacktrace analysis.
Suite du fil

Even though I disabled the JavaCompile task in my conventions file, #Gradle will complain about the inconsistent JDK version between compileJava (unused) and compileKotlin unless I set "java.sourceCompatibility".
Why?

I've never really paid attention to #Gradle before. I know Maven fairly well and has covered much of my needs.

So far, my experience kinda sucks.

The automatic migration from Maven skip two thirds of the useful bits (it did not detect it was a Kotlin project, no compilation or test execution runs).
The answer in the forums are quite passive-aggressive and every Gradle newcomer seems to be struggling with the same things :/

I sincerely hope it gets better.

🚀 New Blog Post: NixOS Meets Enterprise Java – A Cautionary Tale ☕❄️

Running an enterprise Java application on NixOS sounded like a great idea—until we hit major roadblocks with Gradle support and authenticated resources. In this post, I share what went wrong, how we fixed it, and why NixOS is still the best option for managing bare metal and VM infrastructure.

Read now 👉 britter.dev/blog/2025/02/27/ni

britter.devNixOS Meets Enterprise Java: A Cautionary TaleIn this blog post I explore the challenges of running an enterprise Java application on NixOS, highlighting issues with Gradle support and authenticated resources. I share lessons learned, workarounds, and why NixOS remains a powerful choice for managing infrastructure despite these hurdles.
#NixOS#Java#Gradle

Been playing around with numtide's blueprint and devshell to set up a dev environment for a #Gradle application - turns out, it's pretty fun! 🎉

What started as just a simple #DevShell ended up with pre-commit hooks, a basic gradle derivation and a #NixOS module with tests.
This should be a good starting point for my next projects.

#Nix continues to be a rabbit hole I love falling into 🌀

github.com/raphiz/gradle-nix-e

GitHubGitHub - raphiz/gradle-nix-example: Kotlin + Gradle + Nix = ❤️Kotlin + Gradle + Nix = ❤️. Contribute to raphiz/gradle-nix-example development by creating an account on GitHub.

🚀 New Blog Post! 🚀

I've been working on optimizing Gradle build support in nixpkgs! In my latest post, I take a deep dive into how it currently works, the limitations of the existing approach, and an optimization that improves efficiency and maintainability.

Check it out here: britter.dev/blog/2025/02/19/ni

I’d love to hear your thoughts! Also, if your team needs Gradle or NixOS consulting, I’d be happy to help. 😊

britter.devOptimizing Gradle Build Support in nixpkgsThis is another blog post that covers the intersection between Gradle and NixOS. This time we look at an optimization I made to the Gradle build support in nixpkgs.
#Gradle#NixOS#nixpkgs