Fix build-time config detection for relocated properties and for config properties from extension deployment modules

[michalvavrik]

Summary

closes: #1149

the script is based on https://github.com/quarkusio/quarkus/blob/main/docs/src/main/java/io/quarkus/docs/generation/AllConfigGenerator.java

Please check the relevant options

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Dependency update
• [ ] Refactoring
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] This change requires a documentation update
• [x] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• [x] Example scenarios has been updated / added
• [x] Methods and classes used in PR scenarios are meaningful
• [x] Commits are well encapsulated and follow the best practices

[michalvavrik]

run tests

[michalvavrik]

run tests

[michalvavrik]

JVM build - Latest Version also fails over it in a daily build.

[rsvoboda]

How often do we need to have the list updated? Is there any noticeable milestone?

Maybe adding a note into https://github.com/quarkus-qe/quarkus-test-framework/blob/main/RELEASE.md#preconditions for new major/minor releases?

CC @mjurc

[michalvavrik]

How often do we need to have the list updated? Is there any noticeable milestone?

strange how it is most of the build-time and build-time-fixed properties are placed in classes in the runtime modules (for build-time it's waste...). and there, it is still automated. then it is not going to fail as long as other bulid-time property or custom class/dependency is detected.

so I'd say:

• you only need to update it if you need to add a property there because your newly added test is failing
• in theory sometimes build-time properties can be moved to runtime, so it would be useful to update it from time to time so that we don't force custom build; this scenario is very unlikely and I wouldn't spend time on it unless I had it

Maybe adding a note into https://github.com/quarkus-qe/quarkus-test-framework/blob/main/RELEASE.md#preconditions for new major/minor releases?

Honestly, we had build-time list for years and we only updated it when we had failing tests. I suppose I could write a workflow that updates it periodically but we don't have this kind of time.

I think we should update it when there is a failure and then when we have a time.

JVM build failure goes down to the https://github.com/quarkusio/quarkus/pull/36826

[rsvoboda]

Cool, seems it's fine to have this as adhoc action.

strange how it is most of the build-time and build-time-fixed properties are placed in classes in the runtime modules (for build-time it's waste...)

Worth GH issue?

[michalvavrik]

strange how it is most of the build-time and build-time-fixed properties are placed in classes in the runtime modules (for build-time it's waste...)

Worth GH issue?

I run quick check and only found 6 examples of this. However additionally, build-time-runtime-fixed is placed in the runtime so it is auto-detected.

as for opening issue - sadly config classes are treated as part of the API now, which is one of the reasons why there is so long process of migrating config classes to config mapping interfaces (in addition to reflection registration effectiveness), so:

• they won't be ale to move it in case other extension is using it (either quarkiverse or custom)
• they can say it when config phase changes they don't have to change class package (move it)

[galderz]

JVM build failure goes down to the quarkusio/quarkus#36826

What failure? The CI failure?

[michalvavrik]

JVM build failure goes down to the quarkusio/quarkus#36826

What failure? The CI failure?

We have one build failure in the JVM build - Latest versions of this PR CI with message Could not find goal 'native-image-agent' in plugin io.quarkus.platform:quarkus-maven-plugin:3.11.0 among available goals , my colleague @jedla97 described it in here https://github.com/quarkusio/quarkus/issues/40951.

[galderz]

JVM build failure goes down to the quarkusio/quarkus#36826

What failure? The CI failure?

We have one build failure in the JVM build - Latest versions of this PR CI with message Could not find goal 'native-image-agent' in plugin io.quarkus.platform:quarkus-maven-plugin:3.11.0 among available goals , my colleague @jedla97 described it in here quarkusio/quarkus#40951.

Not a bug

[michalvavrik]

JVM build failure goes down to the quarkusio/quarkus#36826

What failure? The CI failure?

We have one build failure in the JVM build - Latest versions of this PR CI with message Could not find goal 'native-image-agent' in plugin io.quarkus.platform:quarkus-maven-plugin:3.11.0 among available goals , my colleague @jedla97 described it in here quarkusio/quarkus#40951.

Not a bug

got it, thanks for your time

[michalvavrik]

LGTM - just verifying - the CI failure is caused by wrong Quarkus platform bom version in action?

we need the plugin to use correct version, Jakub tries to address it here https://github.com/quarkus-qe/quarkus-test-framework/pull/1157 (I'll review soon); I wouldn't be worried about this failing as this PR is not specific to Quarkus version and released version was green.