`<extensions>true</extensions>` may fail in CI if added to an integration test pom

[sberyozkin]

Describe the bug

See #51372, this PR's build was keeping failing and only passed after <extensions>true</extensions> was removed.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @quarkusio/devtools (maven)

[sberyozkin]

@Sanne @aloubyansky FYI, perhaps the warning can be removed when the integration tests are run ?
Otherwise, as with the linked #51372, CI builds may start failing and it is quite hard to detect why

[Sanne]

Why was it failing?

[sberyozkin]

As far as I recall it would fail at the documentation build step, @wjglerum do you recall any details ?

Sanne, perhaps you can try a dedicated PR that adds only <extensions>true</extensions> to the pom of that test ?

[aloubyansky]

No, we can't enable extensions in the Quarkus codebase itself.

[sberyozkin]

Thanks @aloubyansky, so I guess we should tune that warning further to avoid it being shown during the integration tests run, I was definitely considering adding it myself and it is shown every time I run some integration tests...

FYI, I suggested to Sanne to open a dedicated PR to see why it was failing, to answer his question

[wjglerum]

As far as I recall it would fail at the documentation build step, @wjglerum do you recall any details ?

Sanne, perhaps you can try a dedicated PR that adds only <extensions>true</extensions> to the pom of that test ?

It happened both for the Documentation CI and Quarkus CI, both for the step:
Populate the .m2 repository (for cache and for shipping to follow-up builds)
See https://github.com/quarkusio/quarkus/actions/runs/19924799617/job/57121812996#step:11:93

[wjglerum]

Error:    The project io.quarkus:quarkus-integration-test-oidc-dev-services:999-SNAPSHOT (/home/runner/_work/quarkus/quarkus/integration-tests/oidc-dev-services/pom.xml) has 1 error
Error:      Unresolveable build extension: Plugin io.quarkus:quarkus-maven-plugin:999-SNAPSHOT or one of its dependencies could not be resolved:
Error:      	Could not find artifact io.quarkus:quarkus-maven-plugin:jar:999-SNAPSHOT
Error:      -> [Help 2]
org.apache.maven.plugin.PluginManagerException: Plugin io.quarkus:quarkus-maven-plugin:999-SNAPSHOT or one of its dependencies could not be resolved:```

[wjglerum]

Thanks @aloubyansky, so I guess we should tune that warning further to avoid it being shown during the integration tests run, I was definitely considering adding it myself and it is shown every time I run some integration tests...

Yeah that would be helpful indeed. Especially that it does work locally if you do this 😄

[Sanne]

I'm not understanding what leads you to think that this particular warning about the extensions is failing the build.
To be clear, it wasn't merged yesterday - it's been more than two weeks. I assume other PRs have been fine, or are you saying that no CI job could complete successfully for weeks?

[aloubyansky]

AFAIU, they are trying to enable extensions in the Quarkus repo itself.