Don't publish integration tests during a Maven release

[zregvart]

Currently integration test artefacts such as camel-quarkus-integration-test-aws are published with the release. I think for 1.0 release we should not publish those. This can be done by adding:

<plugin>
  <artifactId>maven-deploy-plugin</artifactId>
  <configuration>
    <skip>true</skip>
  </configuration>
</plugin>

To https://github.com/apache/camel-quarkus/blob/master/integration-tests/pom.xml

[ppalaga]

Yes, publishing the itests is typically useless, but in our case, it was a deliberate decision, because they are run inside quarkus-platform https://github.com/quarkusio/quarkus-platform/tree/master/integration-tests

[ppalaga]

Can we close this one, @zregvart ?

[zregvart]

Is there a use case for them being published to Maven Central, are users depending on them? If not perhaps the <skip> can be added in the release profile.

[oscerd]

They are used here https://github.com/quarkusio/quarkus-platform/tree/master/integration-tests as dependency. So they must be released.

[ppalaga]

It works as designed. Feel free to reopen if you feel the design is not correct.