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

mvn io.quarkus:quarkus-maven-plugin:1.7.1.Final:list-extensions is not working from non-quarkus directory #11805

Closed
rsvoboda opened this issue Sep 2, 2020 · 8 comments
Labels
area/maven kind/bug Something isn't working triage/needs-feedback We are waiting for feedback.

Comments

@rsvoboda
Copy link
Member

rsvoboda commented Sep 2, 2020

mvn io.quarkus:quarkus-maven-plugin:1.7.1.Final:list-extensions is not working from non-quarkus directory
It works when executed in directory with pom.xml which is using Quarkus

mvn io.quarkus:quarkus-maven-plugin:1.3.4.Final:list-extensions works from any path
For newer version it worked for Quarkus 1.5.0, not working since Quarkus 1.6.0

@rsvoboda rsvoboda added the kind/bug Something isn't working label Sep 2, 2020
@quarkusbot
Copy link

/cc @quarkusio/devtools

@rsvoboda
Copy link
Member Author

rsvoboda commented Sep 2, 2020

My use case is to get quickly the list of latest extensions, I know that using mvn io.quarkus:quarkus-maven-plugin:1.3.4.Final:list-extensions I won't get the list of extensions for Quarkus 1.3.4.Final, I would need to have project using Quarkus 1.3.4.Final and call mvn quarkus:list-extensions.

@gastaldi
Copy link
Contributor

The following stacktrace is displayed when mvn quarkus:list-extensions is executed outside a project directory:

Caused by: io.smallrye.beanbag.NoSuchBeanException: No matching bean available: type is interface org.apache.maven.settings.crypto.SettingsDecrypter
    at io.smallrye.beanbag.Scope.getBean (Scope.java:259)
    at io.smallrye.beanbag.Scope.requireBean (Scope.java:164)
    at io.smallrye.beanbag.BeanBag.requireBean (BeanBag.java:85)
    at io.quarkus.bootstrap.resolver.maven.BootstrapMavenContext.initRepoSystemAndManager (BootstrapMavenContext.java:884)
    at io.quarkus.bootstrap.resolver.maven.BootstrapMavenContext.getRepositorySystem (BootstrapMavenContext.java:292)
    at io.quarkus.bootstrap.resolver.maven.MavenArtifactResolver.<init> (MavenArtifactResolver.java:91)
    at io.quarkus.bootstrap.resolver.maven.MavenArtifactResolver$Builder.build (MavenArtifactResolver.java:74)
    at io.quarkus.registry.ExtensionCatalogResolver$Builder.completeConfig (ExtensionCatalogResolver.java:106)
    at io.quarkus.registry.ExtensionCatalogResolver$Builder.build (ExtensionCatalogResolver.java:89)
    at io.quarkus.devtools.project.QuarkusProjectHelper.getCatalogResolver (QuarkusProjectHelper.java:166)
    at io.quarkus.maven.QuarkusProjectMojoBase.getExtensionCatalogResolver (QuarkusProjectMojoBase.java:145)
    at io.quarkus.maven.QuarkusProjectMojoBase.resolveExtensionCatalog (QuarkusProjectMojoBase.java:130)
    at io.quarkus.maven.QuarkusProjectMojoBase.execute (QuarkusProjectMojoBase.java:111)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:904)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:281)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:204)

@geoand
Copy link
Contributor

geoand commented Sep 13, 2024

Is this still an issue?

@geoand geoand added the triage/needs-feedback We are waiting for feedback. label Sep 13, 2024
@aloubyansky
Copy link
Member

#43212 should fix it

@aloubyansky
Copy link
Member

At least the issue @gastaldi reported

@rsvoboda
Copy link
Member Author

fixed by #43212

Both list-platforms and list-extensions work

mkdir tmp
cd tmp
mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:list-platforms
mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:list-extensions

@geoand
Copy link
Contributor

geoand commented Sep 13, 2024

🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/maven kind/bug Something isn't working triage/needs-feedback We are waiting for feedback.
Projects
None yet
Development

No branches or pull requests

5 participants