-
Notifications
You must be signed in to change notification settings - Fork 6
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
lateinit property nexusClient has not been initialized #524
Comments
Ah! Drop was not designed to be used alone. I need to look into this |
Can you provide a build scan? |
|
We need to rethink what the plugin is meant to do, because it is currently designed for a single-run pipeline maven-style. Nexus related operations:
This should support both a "one shot" pipeline and a multi-stage pipeline, doesn't it? |
@nicolasfara I prepared a patch in #525, but I'd like to have a regression test before merging. Can you prepare an additional test to be performed in CI and target branch |
Fixed in #525 which will be merged soon. Reopen if the fix does not work. |
## [3.3.3](3.3.2...3.3.3) (2023-03-04) ### Bug Fixes * **drop:** drop now depends on staging repository creation, and runs after all uploads. Fixes [#524](#524) ([41d00ba](41d00ba)) ### Build and continuous integration * fix indentation ([8a1a7bc](8a1a7bc)) * **test:** add regression test on drop gradle task ([a147f2b](a147f2b)) ### Dependency updates * **deps:** update plugin publishoncentral to v3.3.2 ([74ba25d](74ba25d))
🎉 This issue has been resolved in version 3.3.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
When executing
./gradlew drop
the following error is raised:The text was updated successfully, but these errors were encountered: