Maven failing with GitHub Packages

[coppolaop]

Select Topic Area

Question

Body

Hi team! I'm trying to import a package from my github to a new project. I'm following this article: https://docs.github.com/pt/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.
The project i've been trying to access is this one: https://github.com/coppolaop/RPGDiceRoller/packages/212323
Here is my Settings.xml:

And here is my pom.xml:

Personal access tokens (classic) has permission to write and read packages.
I'm using Intellij to integrate with maven but i also tried via cmd. Settings.xml is running just like it needs to run:

I asked my friend to do the same process in her desktop, and she is having the same issue as me:

I look for something in the net but there is anything available that helps.
Anyone knows how to solve this?

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[coppolaop]

There is no solution yet

[martinondiwa]

The issue you’re encountering when importing the package from GitHub into your project using Maven could be caused by several things. I'll walk you through troubleshooting steps based on the provided information. Here's how to solve it:

1. Ensure Correct Configuration of settings.xml:
   Check that your settings.xml file is correctly configured for GitHub's Apache Maven repository. The essential elements to check are:
   1.GitHub Package Registry URL: Make sure you're using the correct GitHub Package Registry URL, like this:
   xml
   Copy code

github https://maven.pkg.github.com/OWNER/REPOSITORY Replace OWNER and REPOSITORY with your GitHub username and repository name. 2. Authentication: Your settings.xml should include a server entry for GitHub with the correct credentials (username and personal access token). It should look like this: xml Copy code github YOUR_GITHUB_USERNAME YOUR_PERSONAL_ACCESS_TOKEN 3. Personal Access Token (PAT): Make sure that your personal access token (PAT) has the necessary permissions for repo, read:packages, and write:packages. You can verify the permissions by checking the token settings in GitHub. 4. Ensure the Correct Configuration in pom.xml: Your pom.xml should reference the repository from which you want to pull the package. Ensure that the repository details match those in your settings.xml. Here’s an example: xml Copy code github https://maven.pkg.github.com/OWNER/REPOSITORY Make sure that the section in your pom.xml points to the correct version of the package you're importing. 5. Check Repository and Artifact Names: Verify that the package (artifact) you're trying to pull exists in the specified GitHub repository. Double-check the groupId, artifactId, and version in your pom.xml match the package’s details in GitHub Packages. Example: xml Copy code com.github.coppolaop RPGDiceRoller 1.0.0 6. Clean and Rebuild the Project: Sometimes Maven can have issues with cached data. Try cleaning your project and rebuilding it. You can do this with: bash Copy code mvn clean install Also, try deleting your local .m2 repository to ensure you're pulling the latest versions. 7. Proxy and Firewall Settings: If you are behind a proxy or firewall, it might block the connection to GitHub’s Maven package registry. Make sure that Maven can reach GitHub and that your network settings allow it. 8. Test in Command Line: Since you're using IntelliJ, try running the Maven commands directly from the command line to isolate whether IntelliJ or its Maven integration is causing the issue. Use: bash Copy code mvn install Check the logs for detailed errors. By checking these configurations, you should be able to troubleshoot why you're unable to import the package. If you still run into problems, posting the exact error messages (from the IntelliJ console or the command line) will help pinpoint the issue.

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[coppolaop]

While I'm trying to execute all of @martinondiwa suggestions, I notice something wrong in my package. I dont know why, but my package group ID is repeating the artifact ID.

all this time I blamed the maven configuration, but the problem was the package itself (maybe because of the camelcase name).
I just removed the project name on group id and it was solved.
Maybe it's a GitHub problem, maybe it is my package configuration. But now, it's working!
If you found this discussion, look to your package group ID.