"It appears that between 5.0 and 5.1, using a classifier when publishing JARs using the Maven Publishing plugin has been deprecated. I mention this because many of the fields are now marked deprecated in the v5.1 docs 6, but they were not in the v5.0 docs 2. I didn’t however see any mention of this deprecation in the v5.1 release notes"
I put together productivity tips for using some of my favourite tools in this video. Which of these do you already use everyday? Did you learn something new?
After 3,5 years of working with #gradle I'm back with #maven and one thing I'm enjoying is the uniformity of how to configure Maven. With Gradle, it seems there are several ways of doing the same thing, and they don't all work when combined.
TIL about #Asimov, a tool to exclude build target folders for various tech stacks from a #TimeMachine backup. Be sure to install the latest head (for #Gradle support) and have your folder permissions set correctly (I had to fix mine to see my projects). https://github.com/stevegrunwell/asimov
At a job interview, I was asked why I prefer @ASFMavenProject over @Gradle and here's another example: I am facing a minor issue with https://github.com/detekt/detekt . Nothing big, in fact, fixing the issue is a matter of 10 lines of code. Nevertheless, it's a show-stopper for me, so, I can't wait for my PR to be merged. So, what do I do? I clone the repo onto our private GitLab, change the group-id and publish a patched version of detekt into our internal maven repo.
@ASFMavenProject@Gradle
Easy with #Maven, not so much with #Gradle: Because Gradle allows for so much customization, the build is very hard to understand for anyone not familiar with the project. In this case, changing the group-id (which should only be used during publishing the artifacts) also broke some tests for whatever reason. And even though I did a project-wide search and replace, I was unable to find that broken dependency.
I'm glad to see efforts to have a clearer separation between build definition and build logic in #gradle. There has been huge progress in terms of guidance in the past years, but no enforcement. This is a step forward!
JetBrains introduces Amper. An experimental project description language for #Kotlin Multiplatform. The underlying system using the notation is still #Gradle.
Happy to see such developments. The #Java / #JVM build system is Gradle's killer application. But in its core it's a powerful framework to create build systems on top of.
The huge feature set of vanilla Gradle is probably it's biggest weakness when used directly by end users. Excited to see where this goes.
Hi Gradle users, I have a question. How do you replace or update a transitive dependency?
Is the preferred way to register the transitive dependency as a direct one, or are there better ways?
Is there an equivalent to dependencyManagement in Maven? #gradle#java#dependencies
Planning a new article on #Kotlin, #Javalin, #HTMX, #TailwindCSS, #Playwright. Probably #Gradle, although I'm more and more interested in rediscovering #Maven. Maybe #RetroFit to include some OHS/ACL (#DDD Context Mapping), but maybe this is already a lot to combine just for an exploration.
A few years back, I wrote a #Java Magazine article with an accompanying Github repo to explore using #Gradle modules to express & enforce #hexagonalarchitecture
Today I attended a talk by Damir Murat where he explained a demo project, Klokwrk, where he explores a code folder structure to express #DDD. He calls it Strategic Structure, referring to Strategic DDD with domains and bounded contexts. It's quite detailed, and I like this approach.
I made an almost certainly silly thing. It's a #maven plugin to support building #gradle modules in an otherwise maven project. Crazy? Maybe but it scratches an itch of mine. :)
#Gradle supports different options to write plugins. This is good, because it gives you the choice to use what fits your context. Any you should always write plugins - if only to organize your project's build configuration.
I like #gradle all right (given it's a build tool that's a compliment 😆) but I've been always annoyed with the groovy to #kotlin conversion for little tasks I need.
ChatGPT was very helpful today. A use-case I had not considered yet!
I use the HTTP request actions in #Tasker to automate the creation of time entries in #Toggl, but that's been pretty darn flaky for me recently. Not sure if that's my internet, my phone, or Toggl's API blocking my requests.
Tasker provides a library and POC code for creating native plugins. So, let's try that! It's an excuse to get back into some #Flutter development, and it'll force me to get exposed to #Gradle and #Kotlin.
In this post, I’d like to shed some light on my stance regarding #gradle, so I can direct people to it instead of debunking the same "reasoning" repeatedly.
Video version of Tales from the jar side, for the week of July 10 - 17, 2023. Creating and expanding zips and jars in Gradle (featuring Groovy vs Kotlin), experiments with AI, and the usual silly assortment of tweets, toots, skeets, etc