integration-tests - Use the right version of quarkus-maven-plugin in the native profile

[jaikiran]

The commit here should fix the issue reported in #4836.

Ideally, I think, the parent pom.xml of the integration tests should probably dictate this in pluginManagement for the native profile too. But I couldn't get that working. Nor do I see any conclusive documentation that the pluginManagement for profiles is supported from the parent pom.xml. So at least for now, this goes directly in the vault-app's native profile in pom.xml

[gsmet]

Could you do a quick sanity check that it’s not an issue with some other ITs? And that our Pom templates generating the projet poms are Ok? They are ftl files.

[vsevel]

Could you do a quick sanity check that it’s not an issue with some other ITs?

hello @gsmet I found quite a few. see #4836 (comment)
can't say if sometimes they are legitimate though

[jaikiran]

Could you do a quick sanity check that it’s not an issue with some other ITs?

I did some manual checks and found a bunch of them in the integration-tests that were missing the version. I've updated this PR to include them.

I was really hoping we could set this native profile in the parent pom.xml and then add pluginManagement there, just like with the default build/profile, but that isn't working for me. Maybe @aloubyansky would know if that's supported?

As for the ftl files which we use to generate some of these pom.xml files, I had a look at them in the devtools/templates and those rightly use the ${quarkus.version} for the quarkus-maven-plugin in them. So this all looks like hand generated pom.xml errors.

[geoand]

There will be a parent pom eventually AFAIK, but not soon.

[jaikiran]

There will be a parent pom eventually

Hello @geoand, there in fact is a parent pom.xml in the integration-tests directory. It's just that the plugin versions within a specific profile of child projects don't seem to be managable through top level pluginManagement in the parent pom.xml nor through adding a specific native profile in the parent pom.xml

[geoand]

Ah sorry, I thought you were referring to a general parent pom.

[gsmet]

It looks like a Maven issue to me but if we have at least one Maven version having this problem, we need a workaround anyway.

Thanks for working on this!