Skip to content
Discussion options

You must be logged in to vote

I have had this issue in the past where re-running the workflow or bumping release version resolved the issue.

Otherwise, i think it is recommended to use GitHub workflow with project workspace, settings.xml, & GH token for mvn commands package & deploy via maven/gradle wrappers.

Workflow Snippet

- name: Build with Maven
      run: ./mvnw -B package --file pom.xml

- name: Publish to GitHub Packages Apache Maven
  run: ./mvnw deploy -s $GITHUB_WORKSPACE/settings.xml
  env:
    GITHUB_TOKEN: ${{ github.token }}

See sample packages here that may help narrow the issue:

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by travkin79

This comment was marked as off-topic.

Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Packages Host your dependencies, libraries, and production-ready code, right from your repository Question Ask and answer questions about GitHub features and usage
3 participants