Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How would I correctly reference dependencies #78

Open
vincentsijben opened this issue Mar 24, 2025 · 3 comments
Open

How would I correctly reference dependencies #78

vincentsijben opened this issue Mar 24, 2025 · 3 comments

Comments

@vincentsijben
Copy link
Contributor

So I am in the process of updating my Processing Library. It uses 2 other Processing libraries (Arduino and Minim). My library adds some functionality or helper functions.

To be able for the release.yml GitHub action to successfully build or run the buildReleaseArtifacts task, it needs to have those dependencies as well. How would I organize this in the new library template?

For development obviously I could use the // compileOnly(fileTree("$sketchbookLocation/libraries/<library folder>/library")) part in build.gradle.kts, but the GitHub action cant use this 😄

So the only thing I can think of, is that I copy arduino.jar and minim.jar from my local libraries folder, put them inside the project, for instance inside /src/main/java/libraries/ and use compileOnly(fileTree("src/main/java/libraries")) to get rid of all errors. This works perfectly, but it doesn't feel right to copy library jar files just for releasing purposes.

In the previous "Ant template" approach, I didn't have this problem. I had to manually fix all the correct things to be able to release it. So the automation of the new approach is awesome, but I can't get my head around the go to way to fix this nicely...

@Stefterv
Copy link
Collaborator

Great call Vincent, I was also thinking about this already for the Processing Gradle plugin

@mingness
Copy link
Collaborator

@Stefterv is there anything we can do in the short term? I don't have a good idea for a solution yet.

@Stefterv
Copy link
Collaborator

Other than putting the jars in the repo >:) I can't really think of anything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants