Skip to content

Conversation

@aloubyansky
Copy link
Member

Following #51112

@quarkus-bot quarkus-bot bot added area/cli Related to quarkus cli (not maven/gradle/etc.) area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins labels Nov 20, 2025
@quarkus-bot
Copy link

quarkus-bot bot commented Nov 20, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 95949b2.

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
Initial JDK 17 Build Populate the .m2 repository (for cache and for shipping to follow-up builds) ⚠️ Check → Logs Raw logs 🚧

@aloubyansky
Copy link
Member Author

Ah, we actually can't do it in our own repository due to the extension not being available yet in the lifecycle it is expected to be initialized.
FYI @Sanne

@Sanne
Copy link
Member

Sanne commented Nov 21, 2025

What would be the benefit of having it here?

@aloubyansky
Copy link
Member Author

To remove the warning.

@aloubyansky
Copy link
Member Author

Basically, our build logs are flooded with this warning now. Perhaps we should introduce an option to suppress it.

@Sanne
Copy link
Member

Sanne commented Nov 21, 2025

I've checked, this PR becomes effective if one applies #51168 first.

@aloubyansky
Copy link
Member Author

We could also do main...aloubyansky:quarkus:suppress-not-enabled-extensions-warning

If we run mvn test, build won't be executed but if we perform some setup for tests in the extension, it probably makes sense to still log something.

@Sanne
Copy link
Member

Sanne commented Nov 21, 2025

We could also do main...aloubyansky:quarkus:suppress-not-enabled-extensions-warning

sure but this is only useful in a very specific corner case of our own build, do I understand correctly?
We'll still need my other PRs as well, as that affects end users.

@aloubyansky
Copy link
Member Author

We could also do main...aloubyansky:quarkus:suppress-not-enabled-extensions-warning

sure but this is only useful in a very specific corner case of our own build, do I understand correctly?

Yes

We'll still need my other PRs as well, as that affects end users.

You mean #51168? Or more?

DevMojo in some cases invokes other quarkus goals but it passes some parameters to them and can include suppressTheWarning one.

@Sanne
Copy link
Member

Sanne commented Nov 21, 2025

We could also do main...aloubyansky:quarkus:suppress-not-enabled-extensions-warning

sure but this is only useful in a very specific corner case of our own build, do I understand correctly?

Yes

We'll still need my other PRs as well, as that affects end users.

You mean #51168? Or more?

Yes I was referring to #51168 - nothing more.

@aloubyansky
Copy link
Member Author

This would fix quarkus:dev for users

$ git diff
diff --git a/devtools/maven/src/main/java/io/quarkus/maven/DevMojo.java b/devtools/maven/src/main/java/io/quarkus/maven/DevMojo.java
index 6244dbfa97..feebaf1343 100644
--- a/devtools/maven/src/main/java/io/quarkus/maven/DevMojo.java
+++ b/devtools/maven/src/main/java/io/quarkus/maven/DevMojo.java
@@ -838,10 +838,11 @@ private String handleAutoCompile(List<String> reloadPoms) throws MojoExecutionEx
      * @return map of parameters for the Quarkus plugin goals
      */
     private Map<String, String> getQuarkusGoalParams(String bootstrapId, List<String> reloadPoms) {
-        final Map<String, String> result = new HashMap<>(4);
+        final Map<String, String> result = new HashMap<>(5);
         result.put(QuarkusBootstrapMojo.MODE_PARAM, getLaunchModeClasspath().name());
         result.put(QuarkusBootstrapMojo.CLOSE_BOOTSTRAPPED_APP_PARAM, "false");
         result.put(QuarkusBootstrapMojo.BOOTSTRAP_ID_PARAM, bootstrapId);
+        result.put("suppressNotEnabledExtensionsWarning", "true");
         if (reloadPoms != null && !reloadPoms.isEmpty()) {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/cli Related to quarkus cli (not maven/gradle/etc.) area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants