maven-mvnd VS fast-maven-builds

When using build tools like Maven or Gradle, you can configure environment variables in the build scripts or configuration files.

For large projects, purpose-made build tools such as Gradle and Maven are preferred for managing the directory structure since they introduce additional semantics for managing test code and other programming languages (among lots of other things). Most IDEs can integrate with these build tools easily. If you're just starting out though, I wouldn't worry too much about these, you can visit them later.

4.0.0 io.github.mfaisalkhatri selenium-pagefactory-demo 1.0-SNAPSHOT jar selenium-pagefactory-demo http://maven.apache.org UTF-8 4.11.0 7.8.0 3.11.0 3.1.2 17 UTF-8 testng.xml org.seleniumhq.selenium selenium-java ${selenium.java.version} org.testng testng ${testng.version} test org.apache.maven.plugins maven-compiler-plugin ${maven.compiler.version} ${java.release.version} ${maven.source.encoding} true org.apache.maven.plugins maven-surefire-plugin ${surefire-version} test false usedefaultlisteners false ${suite-xml} ${argLine}

Project Build and Management: Apache Maven 3 (3.9.5), Gradle 8 (8.3)

If you are leveraging Maven, use mvnd during development: https://github.com/apache/maven-mvnd

Your tools, such as Maven or Testcontainers, communicate with Podman without reconfiguration.

So how can you configure your Maven build to support such a play lesson? It's easier than you think. Let's start the configuration. My assumption is that you would like to play around with a preview features of JDK21 for example String Templates (JEP430). I just selected this JEP for demonstration. You can select whatever JEP in preview.

SpringWithoutBoot http://maven.apache.org

To compute a helpful baseline, we need a sample project. I created one just for this purpose: it's a relatively small Kotlin project.