-
I was just playing with this and thought I would share what I have found so far.
I am unable to upload classified artifacts, IE sources jar.
I sent in a support request on the classified artifacts being rejected, as well as a request to add gradle to the documentation. My hope is that they will also have decent support for gradle projects producing |
Beta Was this translation helpful? Give feedback.
Replies: 18 comments
-
Hej man any news on that? I have the same issue that my sources.jar gets rejected |
Beta Was this translation helpful? Give feedback.
-
@marvinschramm They responded asking for reproduction steps which I provided and have not heard anything since then. additionally they don’t handle the maven-metadata.xml correctly which results in 400 errors when gradle tries to read what is there before publishing a new snapshot. |
Beta Was this translation helpful? Give feedback.
-
Yea i’ve noticed that. Now we have 1 half published package on our repository which we cant delete… I think we’ll wait until everything is out of beta. Thank you! |
Beta Was this translation helpful? Give feedback.
-
I have the same issues, I’ve had nothing but issues, this looks like such a useful thing but it seems funamentally broken at the moment. |
Beta Was this translation helpful? Give feedback.
-
Same Here! @marvinschramm did it work for u??? |
Beta Was this translation helpful? Give feedback.
-
Same problems from me. I am able to publish the pom files with package registry, but beyond that, everything is rejected. People said that I might need pom properties in my jar, but that doesn’t help in any way. Addiiton of pom properties: The packages with pom only: |
Beta Was this translation helpful? Give feedback.
-
I just ran into the same issue. For me it did upload the build .jar and the .pom file but it rejected the sources and javadoc. The publication can be found here: https://github.com/guthix/Jagex-Store-5/packages/32130. |
Beta Was this translation helpful? Give feedback.
-
@trevjonez Running into the same issue as well. Support ticket in but nothing yet. Any updates on your side? |
Beta Was this translation helpful? Give feedback.
-
I got an initial response that was “can you give a reproduction example” for the classified artifact issue, which I gave them immediately. Radio silence since then. here is my reproduction: https://github.com/trevjonez/github-registry-repro as well as a gradle scan of the issue happening: https://scans.gradle.com/s/eqnfwqbyopiyu/ while doing the reproduction I also found that republishing snapshots fail when querying the maven metadata which is shown in this scan: https://scans.gradle.com/s/5dgkmj22kdgls All of this was August 22 2019 |
Beta Was this translation helpful? Give feedback.
-
I’ve exactly the same issue. Have you found any solution? |
Beta Was this translation helpful? Give feedback.
-
This should work now I forked your project and ran https://github.com/clarkbw/github-registry-repro/packages/38910 BTW we’ve added a new help section for Gradle here: https://help.github.com/en/articles/configuring-gradle-for-use-with-github-package-registry |
Beta Was this translation helpful? Give feedback.
-
Hey @clarkbw, Still having issues with this on my end. When declaring the implementation for this in an Android project, how are you writing it so it finds the files? I can’t seem to get it to point to the files in that fork of yours correctly for the life of me. Have tried
and pretty much every other variation I can think of. Have set up the maven url to point to the repository correctly and provided authentication, but its not constructing a valid path to get the files from. Any help would be greatly appreciated! Edit: This is now working, my error was when setting the url in the maven block, we were only including the OWNER in the url, not the OWNER/REPOSITORY (on both the publishing and implementation sides). Though this does lead to published packages having the repository name in the name of the package itself, which isn’t ideal, it fixes it enough to use which is great. |
Beta Was this translation helpful? Give feedback.
-
Hi @clarkbw, thanks for posting this. FYI the Kotlin DSL instructions are broken on Gradle 5.6.3. I had to change this line:
to:
|
Beta Was this translation helpful? Give feedback.
-
This does not appear to be solved. I’m still seeing this issue with my project. |
Beta Was this translation helpful? Give feedback.
-
can you be more specific about your issue? |
Beta Was this translation helpful? Give feedback.
-
I have tried to publish a package from actions by running “gradle publish”, but is getting:
build.gradle.kts looks like this:
Actions build.yml looks like this:
|
Beta Was this translation helpful? Give feedback.
-
I figured it out. I just had to add the properties to the gradle command in build.yml myself, like so:
|
Beta Was this translation helpful? Give feedback.
-
I ended up using
Basically the same thing, just throwing that out there :slight_smile: |
Beta Was this translation helpful? Give feedback.
This should work now
I forked your project and ran
gradle publish
which works without errors.https://github.com/clarkbw/github-registry-repro/packages/38910
BTW we’ve added a new help section for Gradle here: https://help.github.com/en/articles/configuring-gradle-for-use-with-github-package-registry