Publish Processing Gradle plugins - #1405
Merged
catilac merged 6 commits intoFeb 17, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Stefterv
force-pushed
the
gradle-publishing
branch
from
4fbf4c7 to
cbf9034
Compare
February 6, 2026 08:24
catilac
approved these changes
Feb 6, 2026
Copy link
Copy Markdown
Member
Author
|
I will update this one to also support #1233 |
Sorry, something went wrong.
Stefterv
force-pushed
the
gradle-publishing
branch
from
f7051d1 to
58412ca
Compare
February 7, 2026 12:23
Add a publish-gradle job to the release workflow to publish Processing libraries to the Gradle Plugin Portal using gradle publish with required secrets and version/group env vars. Update gradle/plugins/library/build.gradle.kts to use the com.gradle.plugin-publish plugin, provide plugin metadata (website, vcsUrl, displayName, description, tags) and make the plugin id dynamic ("$group.library"). These changes enable automated publishing of the Gradle plugin with the metadata required by the portal.
Stefterv
force-pushed
the
gradle-publishing
branch
from
58412ca to
0cf146a
Compare
February 7, 2026 12:26
Stefterv
force-pushed
the
gradle-publishing
branch
from
8467f4e to
cc780cf
Compare
February 7, 2026 12:34
Expose the project's group to test JVMs by configuring tasks.withType<Test>() to set systemProperty("project.group", group ?: "org.processing"). Update ProcessingPluginTest to read the plugin id from System.getProperty("project.group") instead of hardcoding the group. Also close the publishing block in build.gradle.kts. This allows tests to adapt when the project group is overridden.
Copy link
Copy Markdown
Member
Author
|
I added the Processing Gradle Plugin publishing |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a publish-gradle job to the release workflow to publish Processing libraries to the Gradle Plugin Portal.
This way future processing libraries can be created by adding
plugins{ id("org.processing.library") version "4.5.3" } processing { library { version = 1 prettyVersion = "1.0.0" authors = mapOf( "The Processing Foundation" to "https://processing.org" ) url = "https://processing.org/" categories = listOf("file", "exporter", "dxf") sentence = "DXF export library for Processing" paragraph = "This library allows you to export your Processing drawings as DXF files, which can be opened in CAD applications." } }To any standard Java/Kotlin gradle project, this will then handle packaging the library. We can add more functionality to it over time and the only thing library authors will need to do is update the plugin version.
TODO:
After merge:
Related:
#1347
#1233