Skip to content

Processing Gradle Plugin 4.5.6 - Missing artifact :utils #1568

Description

@BarracudaLake

Most appropriate sub-area of Processing 4?

I'm not sure

Processing version

4.5.6 ( 4.5.3 )

Operating system

Linux - Fedora 46

Bug description

Could not find org.processing:utils:4.5.6, therefore unable to build root

Followed the following document: https://github.com/processing/processing4/tree/main/java/gradle

Steps to reproduce this

  1. Create a new gradle project

  2. Use the org.processing.java plugin

  3. Try to build

snippet

build.gradle.kts

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

Tried looking through https://repo.maven.apache.org/maven2/org/processing/ for fitting directories, found none

Would you like to work on the issue?

I’m not sure yet

Activity

  1. Chaitanya-970 commented on Sep 3, 2026

    @Chaitanya-970
    Contributor

    Hey I'd like to be assigned this issue
    can i work on it?

  2. SableRaf commented on Sep 5, 2026

    @SableRaf
    Collaborator

    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

  3. SableRaf commented on Sep 5, 2026

    @SableRaf
    Collaborator

    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

  4. Chaitanya-970 commented on Sep 5, 2026

    @Chaitanya-970
    Contributor

    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.

  5. SableRaf commented on Sep 5, 2026

    @SableRaf
    Collaborator

    @catilac How does @Chaitanya-970's plan sound?

  6. Chaitanya-970 commented on Sep 8, 2026

    @Chaitanya-970
    Contributor

    @catilac @SableRaf

    I've already implemented the solution
    Should i raise a PR or is there a need to change anything from my approach?

  7. catilac commented on Sep 17, 2026

    @catilac
    Collaborator

    @Chaitanya-970 ahh please put up a PR! thank you so much

  8. Chaitanya-970 commented on Sep 18, 2026

    @Chaitanya-970
    Contributor

    @catilac @SableRaf
    I've submitted the PR here: #1572.

    I tested it locally with ./gradlew :app:utils:test and publishToMavenLocal and the artifacts are generating as expected.

    Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions