Adjusted config for removed resources in the ExtensionDescriptorMojo to have valid XML

[aloubyansky]

Follow up to #26025

Now it looks like

      <plugin>
        <groupId>io.quarkus</groupId>
        <artifactId>quarkus-extension-maven-plugin</artifactId>
        <version>${quarkus.platform.version}</version>
        <executions>
          <execution>
            <phase>compile</phase>
            <goals>
              <goal>extension-descriptor</goal>
            </goals>
            <configuration>
              <deployment>${project.groupId}:${project.artifactId}-deployment:${project.version}</deployment>
              <removedResources>
                <artifact>
                  <key>org.acme:acme-resources</key>
                  <resources>META-INF/a</resources>
                </artifact>
              </removedResources>
            </configuration>

[aloubyansky]

fyi @xstefank

[aloubyansky]

@gsmet I marked it for backport, since @xstefank needed it in 1.10.

[xstefank]

I don't have a particular use case for backport. However, LRA wouldn't work by default from the release when resteasy-reactive (and thus required reactive REST client) was made default.

[aloubyansky]

@xstefank I thought you wanted this feature before June 20. If we are not backporting this PR it's going to end up in 1.11 for which we don't have a schedule yet.

[gsmet]

You're talking about 2.10 and 2.11, right? I think we can backport it as it doesn't work very well right now.

[aloubyansky]

Are our Gradle tests unstable lately?

[aloubyansky]

I rebased just to see the effect on the CI.

[quarkus-bot]

Failing Jobs - Building 26f9c40

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: integration-tests/elasticsearch-rest-client 

📦 integration-tests/elasticsearch-rest-client

✖ Failed to execute goal io.fabric8:docker-maven-plugin:0.40.0:start (docker-start) on project quarkus-integration-test-elasticsearch-rest-client: I/O Error

[xstefank]

@aloubyansky @gsmet I have an LRA talk next week at DevoxxPL so if we can backport and have a release where I don't need to explain resteasy vs resteasy reactive in the talk that would be great. But if it's too much effort then nothing serious.

[aloubyansky]

Here we go :)