The Quarkus dev mode increases our development productivity and especially reduces the turnaround times how long it takes to get test feedback. For Quarkus projects, this is a huge benefit. However, with some hacky workarounds, it’s possible to run the tests of a plain Java project also in a similar way.
In this video, I’m showing how to add the Quarkus Maven plugin to non-Quarkus projects:
You can check out the system project in Quarkus version 2.0.0.CR3 on GitHub.
In the system test project, I’ve added the following pom.xml snippet:
<profiles>
<profile>
<id>test</id>
<properties>
<quarkus.version>2.0.0.CR3</quarkus.version>
<debug>false</debug>
<quarkus.native.builder-image>ignored</quarkus.native.builder-image>
</properties>
<dependencies>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-core</artifactId>
<version>${quarkus.version}</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-maven-plugin</artifactId>
<extensions>true</extensions>
<version>${quarkus.version}</version>
<executions>
<execution>
<goals>
<goal>build</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>In this way, we have to activate the test Maven profile when executing the Quarkus plugin:
mvn quarkus:dev -Ptest
Published on Java Code Geeks with permission by Sebastian Daschner, partner at our JCG program. See the original article here: Using the Quarkus dev mode for non-Quarkus projects (Video) Opinions expressed by Java Code Geeks contributors are their own. |
