Skip to content

Could not find org.codehaus.groovy.modules.http-builder:http-builder:0.7.2 #67

Open
Open
Could not find org.codehaus.groovy.modules.http-builder:http-builder:0.7.2#67

Description

@jakub-trzebiatowski
jakub-trzebiatowski
opened on Apr 27, 2025

After attempting to open the project in IntellJ IDEA, I get the following error:

A problem occurred configuring root project 'jcsg'.
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find org.codehaus.groovy.modules.http-builder:http-builder:0.7.2.
     Searched in the following locations:
       - https://plugins.gradle.org/m2/org/codehaus/groovy/modules/http-builder/http-builder/0.7.2/http-builder-0.7.2.pom
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
     Required by:
         project : > com.jfrog.bintray:com.jfrog.bintray.gradle.plugin:1.8.4 > com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4

Possible solution:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

Activity

  1. madhephaestus commented on Apr 28, 2025

    @madhephaestus
    madhephaestus
    on Apr 28, 2025
    Contributor

    This (the original) branch seems to be dead now. I have an actively maintained fork over here: https://github.com/NeuronRobotics/JCSG

  2. jakub-trzebiatowski commented on Apr 28, 2025

    @jakub-trzebiatowski
    jakub-trzebiatowski
    on Apr 28, 2025
    Author

    @madhephaestus Just for clarity, isn't this the original/upstream repository? @miho just replied to me on another thread, so I hope at least he is well and alive 😉 Did you consider contributing your changes in the form of pull requests?

  3. miho commented on Apr 28, 2025

    @miho
    miho
    on Apr 28, 2025
    Owner

    In the past it was relatively complicated for me to accept changes since the library was an important part of a project that had some restrictions regarding API stability/changes, etc. Since a couple of years it's much easier for me to accept changes. But I haven't been actively pulling them in myself. But with a little nagging we could certainly do that :)

  4. madhephaestus commented on Apr 28, 2025

    @madhephaestus
    madhephaestus
    on Apr 28, 2025
    Contributor

    @miho I would love to merge some changes back! I have been continuously developing on my fork. One major change is to make the errors that arose from small triangles go away by passing the plane orientation to new clipped triangles, an algorithm to ensure purely manifold meshes (for Prusa Slicer compatibility) and my much older API additions that make scripted coding of CSG objects much less verbose.

    I am also starting to make a full Parallel compute update using Aparapi which would let users, that have OpenCL enabled, to use the GPU to perform some tasks.

    I have also added many advanced features such a bezier lofts, sweeps, SVG import, SVG export (with outer vector calculations via a slicing algorithm), Text extrude, and many, many more primitive shapes.

    Most recently i have built a click-for-click clone of Tinkercad and used JCSG as the geometry engine under the hood. https://github.com/CommonWealthRobotics/CaDoodle

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions