Use github action to publish jar file

[taojing2002]

We need to use the github action to publish the jar file to the github package registry.

Here is the documentation:
https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-java-packages-with-maven

[taojing2002]

We created the git hub actions to publish the jar file to the github repository.

[vchendrix]

@taojing2002 Looks like the publish action failed. It is a conflict error, which probably means that you need to overwrite the existing jar or something else.

[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/commons-io/commons-io/2.5/commons-io-2.5.jar (209 kB at 2.5 MB/s)
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.1.0/plexus-utils-3.1.0.jar (262 kB at 3.0 MB/s)
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/slf4j/slf4j-api/1.7.5/slf4j-api-1.7.5.jar (26 kB at 287 kB/s)
[INFO] Uploading to github: https://maven.pkg.github.com/NCEAS/osti-elink/edu/ucsb/nceas/osti-elink/2.0.0/osti-elink-2.0.0.jar
[INFO] Uploading to github: https://maven.pkg.github.com/NCEAS/osti-elink/edu/ucsb/nceas/osti-elink/2.0.0/osti-elink-2.0.0.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  8.296 s
[INFO] Finished at: 2025-02-06T20:18:13Z
[INFO] ------------------------------------------------------------------------
Error:  Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) on project osti-elink: ArtifactDeployerException: Failed to deploy artifacts: Could not transfer artifact edu.ucsb.nceas:osti-elink:jar:2.0.0 from/to github (https://maven.pkg.github.com/NCEAS/osti-elink): status code: 409, reason phrase: Conflict (409) -> [Help 1]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error: Process completed with exit code 1.

[taojing2002]

I saw the error messages about the conflict. I think the reason is that I already manually built the 2.0.0 jar two weeks ago. So the system prevent us to build again since it is a formal release. There is no real code change except a test file after the jar file was built. So I haven't taken a look on how to overwrite it. Do you think we need to build the jar file again? @vchendrix

[vchendrix]

You could add paths to ignore in the code base for the gh action. That way it won't try to publish if there were no changes to the jar. It is probably good to have the error in the case where the version was not bumped. +++++++++++++++++++++++++++++++++ Valerie Hendrix ***@***.*** Lawrence Berkeley National Lab Mail Stop: 50B-2239 Room: 50B-2258E Phone: (510) 495-2905 Pronouns: she/hers +++++++++++++++++++++++++++++++++

…

On Fri, Feb 7, 2025 at 10:47 AM Jing Tao ***@***.***> wrote: I saw the error messages about the conflict. I think the reason is that I already manually built the 2.0.0 jar two weeks ago. So the system prevent us to build again since it is a formal release. There is no real code change except a test file after the jar file was built. So I haven't taken a look on how to overwrite it. Do you think we need to build the jar file again? @vchendrix <https://github.com/vchendrix> — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAL4M4KYRRF2AKRSE3W3DXL2OT5UJAVCNFSM6AAAAABVF7KIHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBTG4ZDENRSGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>