downloading or accessing jar files when using GitHub actions for R package check #78570
Replies: 3 comments 1 reply
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Did you get the solution for this @mkoohafkan ? please share your solution with me. I also want to learn how do I download Jar via Java |
Beta Was this translation helpful? Give feedback.
-
My solution was to modify the workflow to download the jars to an appropriate location prior to running R CMD check. Right now the jar versions are hard coded but I think I could change that in the future parse the default config included in the package (probably by hardcoding th link to that file. You might be interested in something like |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I have an R package that provides an interface to some Java classes, and the package provides a helper function to do a one-time download of the required
.jar
files. I also host the package on GitHub and use the R-lib/check-r-package action to run R CMD check on repo push. However, I currently skip the tests when running the check-r-package action because the.jar
files are not available. I would like to get the tests fully running via GitHub actions but I don't know the best approach for this. It seems like my options are:.jar
files to the GitHub repository so that they are accessible by the package tests. But now I'm hosting copies of the jars and I would want users to download them from the original source and not from my repository..jar
files via a separate GitHub action. But this would mean that I have to maintain two versions of the dependency installation.What is the best practice for solving this type of problem?
Beta Was this translation helpful? Give feedback.
All reactions