-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for publishing Android projects #75
Comments
I use GNPP to publish libs to Sonatype and I get the error.After run " ./gradlew publishToSonatype closeAndReleaseStagingRepository".
FAILURE: Build failed with an exception.
` ` typeId | pom-staging and ` ` I guess that GNPP dismiss "Signing Artifacts" stage as the sonatype website shows https://central.sonatype.org/pages/gradle.html . Forget my poor English. |
@cosmos33 In regards to:
Having some "minimal releasable Android project" would be much more efficient to try to pinpoint the issue than playing with "hit & miss". Maybe you can provide one? |
It means the pom is not really valid. It is up to build author to fill all the required information to pom.xml @szpak , what do you think of adding https://docs.gradle.org/current/userguide/publishing_maven.html#sec:modifying_the_generated_pom to the front page of g-n-p-p? |
I just tried with these changes and it seems like it worked |
update: it works as in uploading to staging, but I see this in the output Task :closeAndReleaseStagingRepository SKIPPED |
when running Execution failed for task ':closeSonatypeStagingRepository'.
> No staging repository with name sonatype created |
here's a sample project @szpak https://github.com/jahirfiquitiva/test-library-maven-publish |
@jahirfiquitiva publication will fail without javadoc |
@joebowbeer I have it in another library and still isn't closed and released by this plugin also, the package is uploaded to staging fine, what doesn't work is closing and releasing, just in case it was misunderstood. and also, manually closing and releasing works, so I guess the plugin should also be able to do so? idk |
Hello, I'm gonna go ahead and just shamelessly plug my project here. Each CI run publishes and closes Sonatype staging repo - Still trying to figure out how can I feed Regards, |
Any update on this issue? |
Looking at the report by @jahirfiquitiva in #74, it seems that there is a problem with publishing Android projects. It would be good to have a minimal Android project to play with it and use in e2e tests.
[...] This suggests that GNPP (this plugin) doesn't correctly detect publishing configuration in an Android project. As a result, it doesn't enhance the publishing task to use the explicitly created staging repository and in general - doesn't work.
I don't have an Android SDK installed locally and I would prefer not to setup it. However, if you created/generated (or stripped down the current one) a totally minimal Android project which does nothing, but builds fine and publishes artifacts to Nexus (as your does), I/we could try to take a look at it to solve the problem with GNPP <-> Android project interaction. Otherwise, it could be hard to do anything about that :-(.
It would be best to publish it to a separate GitHub repo with set up GH Actions (to be able to play with it there) and after (hopefully) successful triage and fix, it could be eventually also converted to an automatic regression e2e tests (as we currently have for single and multi-project regular Java builds) to prevent that kind of problems also in the future. Does it sound good for you? :-).
Originally posted by @szpak in #74 (comment)
The text was updated successfully, but these errors were encountered: