Creating standalone Java project using Maven Archetype

Maven archetypes make it easy to start projects with a standard/consistent code structure. Instead of repeating these steps in every blog that needs starting a project, this blog will be used to show common steps used to start new projects using Maven Archetypes. This post focuses on standalone apps.

Create Application structure

The name of artifactId to be changed as per the actual name of the project to be created

cd C:\tvi\Software\workspace_mars
mvn archetype:generate -DarchetypeArtifactId=maven-archetype-quickstart -DgroupId=com.techvalueinsight -DartifactId=standalone-utils -DinteractiveMode=false

1 2	cd C:\tvi\Software\workspace_mars mvn archetype:generate -DarchetypeArtifactId=maven-archetype-quickstart -DgroupId=com.techvalueinsight -DartifactId=standalone-utils -DinteractiveMode=false

Create Folders

Create folders src/main/resources, src/test/resources.

Update pom.xml

Add properties to maintain versions and other variables at one place :

<properties>
    <java.version>1.8</java.version>
    <junit.version>4.12</junit.version>
    <maven.compiler.plugin.version>3.3</maven.compiler.plugin.version>
</properties>

<java.version>1.8</java.version>

<junit.version>4.12</junit.version>

<maven.compiler.plugin.version>3.3</maven.compiler.plugin.version>

</properties>

Dependencies to use the version numbers from properties:

<dependencies>
  <dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>${junit.version}</version>
    <scope>test</scope>
  </dependency>
</dependencies>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

<version>${junit.version}</version>

</dependency>

</dependencies>

Plugin to specify java version as desired:

<build>
  <finalName>standalone-utils</finalName>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <version>${maven.compiler.plugin.version}</version>
      <configuration>
        <source>${java.version}</source>
        <target>${java.version}</target>
      </configuration>
    </plugin>
  </plugins>
</build>

<build>

<finalName>standalone-utils</finalName>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-compiler-plugin</artifactId>

<version>${maven.compiler.plugin.version}</version>

<source>${java.version}</source>

<target>${java.version}</target>

</configuration>

</plugin>

</plugins>

</build>

Import Maven project into Eclipse

Note: This step can be repeated when ever eclipse is not recognizing the changes in pom.xml etc and refresh the project in Eclipse

cd C:\tvi\Software\workspace_mars\standalone-utils
mvn eclipse:clean eclipse:eclipse

1 2	cd C:\tvi\Software\workspace_mars\standalone-utils mvn eclipse:clean eclipse:eclipse

Open Eclipse with C:\tvi\Software\workspace_mars as workspace directory. File –> Import –> Existing Maven Projects. Root Directory C:\tvi\Software\workspace_mars\standalone-utils. Select standalone-utils’s pom.xml

Test

Open App.java (test java code created by Maven) and change its package location to com.techvalueinsight.apps. Right-Click on the file and Run As –> Java Application. It prints the customary ‘Hello World!’

Leave a Reply Cancel reply