plantuml has 2 main variants, a slim standard version, and one which allows to generate pdf. the pdf variant includes additional libraries, which can be used when on the classpath. i included this - but that seems not enough to get it built: java { ... registerFeature("pdf") { usingSourceSet(so…

Some comments from a quick look: you set source encoding for JavaCompile tasks to UTF-8, but you don’t do so for the JavaDoc tasks, they also need the correct source encoding or you might get encoding problems in the generated documentation you don’t allow publishing to maven local without signing…

there is a slightly related question here: [image] Multiple classifier in dependency variant Help/Discuss Hi, I have a project A whose compilation leads to 2 JARS : A jar without classifier A jar with the classifier API containing only tha API classes On my project B, …

And one more, don’t use tasks.withType<Javadoc> { ... } it is eager and defeats task configuration avoidance efforts, better use tasks.withType<Javadoc>().configureEach { ... }

impressive list, thank you! i saw now optional dependencies , and i like how this can be stated in gradle. the goal was not to publish a fat jar into the maven repo, but generate both, the jar for maven, and the fat jar. maybe publish the fat jar on github to make peoples live easier so they do not …

what produces a jar and a jar including the optional dependencies is: plugins { id("com.github.johnrengelman.shadow") version "7.1.2" } tasks.shadowJar { archiveAppendix.set("pdf") archiveClassifier.set("") } > gradle -q clean build \ shadowJar \ generateMetadataFileForMavenPublication…

decided to not use a plugin, just a dedicated task to produce the fat jar, and upload it into github, no publish. but i’d love to sign it. signing { sign(task("pdfJar")) } tasks.create("pdfJar", Jar::class) { .. } when trying to sign it says “no archive task”. does the Jar:class not make it an …

task("pdfJar") creates an eager (not using task configuration avoidance) instance of an ad-hoc task named pdfJar. You then give this task of type DefaultTask to the sign method and so it of course is not an archive task. If you swap it around to tasks.create("pdfJar", Jar::class) { ... } signing …

thank you, changed it like you suggested, and replaced the gpg part with the gradle in memory signing, with if for local. the “sing” task now got a new names, signMavenPublication and signPdfJar and gradle help does not list them. is this a bug in the sign plugin, as it does not list “sign” in grad…

The Sign tasks are usually not called by an end-user manually so they don’t get a category assigned and tasks without category are not shown by gradlew tasks. They are shown by gradlew tasks --all though under the “Other” category.

Build variant, command line

Help/Discuss

soloturn (soloturn) February 12, 2022, 8:29pm 2

there is a slightly related question here:

Topic		Replies	Views
Multi jdk distribution plugin Help/Discuss	9	240	November 16, 2024
Better way to set project properties for plugin use in builds? Help/Discuss	5	737	November 15, 2023
Advise regarding publishing dependent artifacts Help/Discuss	8	145	May 18, 2025
Why does my consumer prefer java 8 variant to java 11 variant while building with Java 11? Help/Discuss	10	21408	November 25, 2021
Maven-publish does not create full features pom.xml Help/Discuss	10	2908	March 13, 2022

Build variant, command line

Related topics