You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
repositories {
mavenCentral()
}
plugins {
kotlin("jvm") version "2.4.20-RC"
id("org.processing.java") version "4.5.6"
}
Additional context
Console (4.5.3)
Build file '/home/aleph/IdeaProjects/wfc/build.gradle.kts' line: 5
Plugin [id: 'org.processing.java', version: '4.5.3'] was not found in any of the following sources:
Console (4.5.6)
A problem occurred configuring root project 'wfc'.
> Could not resolve all artifacts for configuration 'classpath'.
> Could not find org.processing:utils:4.5.6.
Searched in the following locations:
- https://plugins.gradle.org/m2/org/processing/utils/4.5.6/utils-4.5.6.pom
Required by:
buildscript of root project 'wfc-test-backdrooms' > org.processing.java:org.processing.java.gradle.plugin:4.5.6 > org.processing:gradle:4.5.6 > org.processing:preprocessor:4.5.6
Hi @Chaitanya-970, thanks for your interest in helping with this.
We don’t auto-assign issues based on a “please assign me” request alone.
Please first take a look at our contribution guidelines. Then briefly explain how you’d like to approach the issue. Once that’s clear, and an implementation has been agreed upon, a maintainer can assign it to you.
Hi @Chaitanya-970, thanks for your interest in helping with this.
We don’t auto-assign issues based on a “please assign me” request alone.
Please first take a look at our contribution guidelines. Then briefly explain how you’d like to approach the issue. Once that’s clear, and an implementation has been agreed upon, a maintainer can assign it to you.
Hey, I checked out contributing.md sorry for not doing it before
I think i found the problem the Gradle plugin depends on the preprocessor module, which depends on app/utils.
If you look at the other modules like core or preprocessor, they all have a mavenPublishing { } block in their build.gradle.kts that configures them to publish to Maven Central.
But app/utils/build.gradle.kts is missing that block entirely. it has the mavenPublish plugin applied but no actual publishing configuration. So when the plugin tries to pull org.processing:utils:4.5.6 from Maven Central it's just not there.
I'd like to try fixing this.
The change would be just adding the mavenPublishing config to app/utils/build.gradle.kts, matching what the other modules already do (license info, developer info, scm).
Happy to put up a PR if this sounds like the right approach.
Activity
Chaitanya-970 commentedon Sep 3, 2026
Hey I'd like to be assigned this issue
can i work on it?
SableRaf commentedon Sep 5, 2026
Hi @Chaitanya-970, thanks for your interest in helping with this.
We don’t auto-assign issues based on a “please assign me” request alone.
Please first take a look at our contribution guidelines. Then briefly explain how you’d like to approach the issue. Once that’s clear, and an implementation has been agreed upon, a maintainer can assign it to you.
See: https://github.com/processing/processing4/blob/main/CONTRIBUTING.md#making-your-first-contribution
SableRaf commentedon Sep 5, 2026
Hi @Chaitanya-970, thanks for your interest in helping with this.
We don’t auto-assign issues based on a “please assign me” request alone.
Please first take a look at our contribution guidelines. Then briefly explain how you’d like to approach the issue. Once that’s clear, and an implementation has been agreed upon, a maintainer can assign it to you.
See: https://github.com/processing/processing4/blob/main/CONTRIBUTING.md#making-your-first-contribution
Chaitanya-970 commentedon Sep 5, 2026
Hey, I checked out contributing.md sorry for not doing it before
I think i found the problem the Gradle plugin depends on the preprocessor module, which depends on app/utils.
If you look at the other modules like core or preprocessor, they all have a mavenPublishing { } block in their build.gradle.kts that configures them to publish to Maven Central.
But app/utils/build.gradle.kts is missing that block entirely. it has the mavenPublish plugin applied but no actual publishing configuration. So when the plugin tries to pull org.processing:utils:4.5.6 from Maven Central it's just not there.
I'd like to try fixing this.
The change would be just adding the mavenPublishing config to app/utils/build.gradle.kts, matching what the other modules already do (license info, developer info, scm).
Happy to put up a PR if this sounds like the right approach.
SableRaf commentedon Sep 5, 2026
@catilac How does @Chaitanya-970's plan sound?
Chaitanya-970 commentedon Sep 8, 2026
@catilac @SableRaf
I've already implemented the solution
Should i raise a PR or is there a need to change anything from my approach?
catilac commentedon Sep 17, 2026
@Chaitanya-970 ahh please put up a PR! thank you so much
Chaitanya-970 commentedon Sep 18, 2026
@catilac @SableRaf
I've submitted the PR here: #1572.
I tested it locally with
./gradlew :app:utils:testandpublishToMavenLocaland the artifacts are generating as expected.Thanks.