Skip to content
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

Can't release the cli module #63

Open
iocanel opened this issue Mar 8, 2023 · 5 comments
Open

Can't release the cli module #63

iocanel opened this issue Mar 8, 2023 · 5 comments

Comments

@iocanel
Copy link
Contributor

iocanel commented Mar 8, 2023

Ever since I added the cli module to the project, I can't release due to:

Error: [ERROR] Rule failure while trying to close staging repository with ID "ioquarkiverse-1781".
Error: [ERROR] 
Error: [ERROR] Nexus Staging Rules Failure Report
Error: [ERROR] ==================================
Error: [ERROR] 
Error: [ERROR] Repository "ioquarkiverse-1781" failures
Error: [ERROR]   Rule "sources-staging" failures
Error: [ERROR]     * Missing: no main jar artifact found in folder '/io/quarkiverse/authzed/quarkus-authzed-cli/0.2.1'
Error: [ERROR]   Rule "javadoc-staging" failures
Error: [ERROR]     * Missing: no main jar artifact found in folder '/io/quarkiverse/authzed/quarkus-authzed-cli/0.2.1'
Error: [ERROR] 
Error: [ERROR] 
Error: [ERROR] Cleaning up local stage directory after a Rule failure during close of staging repositories: [ioquarkiverse-1781]
Error: [ERROR]  * Deleting context 166ff053e5f61f.properties
Error: [ERROR] Cleaning up remote stage repositories after a Rule failure during close of staging repositories: [ioquarkiverse-1781]
Error: [ERROR]  * Dropping failed staging repository with ID "ioquarkiverse-1781" (Rule failure during close of staging repositories: [ioquarkiverse-1781]).

Details: https://github.com/quarkiverse/quarkus-authzed-client/actions/runs/4364294724/jobs/7631435499

It seems to me that cli is producing an artifact with the classifier runner and there is no unclassified artfiact. Nexus doesn't seem to like it.

@iocanel
Copy link
Contributor Author

iocanel commented Mar 8, 2023

@gastaldi, @gsmet, @geoand: Any ideas here? How do we deal with this issue for the Quarkus CLI itself?

@geoand
Copy link

geoand commented Mar 8, 2023

No ideas here unfortunately

@iocanel
Copy link
Contributor Author

iocanel commented Mar 8, 2023

It seems that quarkus.package.add-runner-suffix might do the trick. 🤞

@gastaldi
Copy link
Member

gastaldi commented Mar 8, 2023

If that doesn't work, you might need to generate your CLI as an uber-jar:

        <quarkus.package.type>uber-jar</quarkus.package.type>

@iocanel
Copy link
Contributor Author

iocanel commented Mar 8, 2023

If that doesn't work, you might need to generate your CLI as an uber-jar:

        <quarkus.package.type>uber-jar</quarkus.package.type>

I already have this in my application.properties.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants