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
This will help in easier integration and accessibility for users who need to include this library in their projects.
Steps to make the jar publicly available:
Ensure that the repository NCEAS/osti-elink is configured to upload packages to GitHub Packages.
Navigate to the repository settings and go to the Packages section.
Check the permissions to ensure that the package is set to be publicly accessible.
Follow the instructions in the GitHub documentation to publish the jar file to the Maven repository.
While the jar file can be downloaded from the UI on the package page, there is no way to build this into a script, making it less convenient for automated builds and deployments.
Thank you!
The text was updated successfully, but these errors were encountered:
So I believe this jar file is publicly accessible since the pom.xml doesn't have any credentials. I am wondering if the url you posted above is a valid or not. I haven't figured out the direct url to download the jar file.
After you download it from the maven repo via your POM reference, you should have a copy of the jar file and all of its metadata in your .m2 directory. I'll bet a reference to the full URL is in that metadata somewhere in .m2
Please make the
osti-elink
jar available for public download from the following Maven repository:https://maven.pkg.github.com/NCEAS/osti-elink/edu/ucsb/nceas/osti-elink/2.0.0/osti-elink-2.0.0.jar
This will help in easier integration and accessibility for users who need to include this library in their projects.
Steps to make the jar publicly available:
NCEAS/osti-elink
is configured to upload packages to GitHub Packages.Packages
section.While the jar file can be downloaded from the UI on the package page, there is no way to build this into a script, making it less convenient for automated builds and deployments.
Thank you!
The text was updated successfully, but these errors were encountered: