GitHub packages: publish to another repository

GitHub Ecosystem
#1

As an example we have the follwing setup:

  • module 1: woodpecker with own source repo on GitHub
  • module 2: roadrunner with own source repo on GitHub
  • module 3: coyote with own source repo on GitHub

We don’t want to have a separate maven definition (in our build.gradle) for each of the modules as this would clutter up the complete build.gradle files. So we thought about having the publish task pointing to one central repository e.g. com.acme.

However in doing so we receive an HTTP 422 error like this one:

org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not PUT ‘https://maven.pkg.github.com/Acme/com.acme/woodpecker/0.0.5/woodpecker-0.0.5.jar’. Received status code 422 from server: Unprocessable Entity

How can this be solved? Many thanks in advance and kind regards

2 Likes
#2

I’m facing the same issue - so this reply is only to raise awareness.

Would be sad if this structure is required :

repositories{  
mavenLocal()
mavenCentral()
maven{  
name ="GitHubPackages"  
url = uri("https://maven.pkg.github.com/some-owner/repo-a")
credentials{  
username = gprUser
password = gprToken
}  
 }  
 maven {  
 name = "GitHubPackages"  
 url = uri("https://maven.pkg.github.com/some-owner/repo-b")  
 credentials {  
 username = gprUser  
 password = gprToken  
 }  
 }  
...  
}
1 Like
#3

It looks like the package group and name must be unique within the user/organization. I got this same error (422) when I tried to publish a previously published package into a new private repository. I tried changing the package name and everything went swimmingly after that.

7 Likes
#4

I’m facing a 422 but happens after publishing. The message is always a 422 even when the package publish.

#5

At least for me, problem was solved when I avoided using uppercase letters in the artifact id. I put all lowercase letters for the group id and the artifact id in the pom file and it worked!

2 Likes
#6

I have been able to publish different artificats from different repos into a shared com.acme repo as the original poster suggested. However if package com.example:foo has been published to repo x and then you try to publish com.example:foo to repo y you get the 422 conflict response code. deleting the package from repo x makes it possible to publish it to repo y. Seems like github packages is enforcing package uniqueness across repos.