build.xml file.pom.xml file.POM file, pom.xml.xml file (%USER_HOME%/.m2/settings.xml).xml file (%M2_HOME%/conf/settings.xml)DAO, SERVICE and WEB. These modules had the required dependencies. All project members used this archetype as it saved a lot of time and every one had same starting workspace.                                                                    JAR, that gets deployed to a Maven repository. A Maven build produces one or more artifacts, such as a compiled JAR and a "sources" JAR.domain name, like com.javainuse), an artifact ID (just a name), and a version string. The three together uniquely identify the artifact.<dependency>
    <groupId> org.selenium </groupId>
    <artifactId> seleniumJava </artifactId>
    <version> 4.0.2 </version>
</dependency>
build.xml. The dependencies of your Java project are automatically downloaded by Maven and stored in a local repository and can be retrieved in quick time, whenever needed. <build/> element of the POM.xml file.  <reporting/> element of the POM.xml file. mvn –versionmvn clean install –Umvn archetype : generate1.0-SNAPSHOT version. In the future, this version will emerge to be 1.0 version. It is called as the present development copy. Maven looks for the new SNAPSHOT version in the remote repository.                                                                    Maven external dependencies are described in the pom xml file just like other dependencies. The parameters required to define the external dependencies are groupid, artifactId, scope set to system and system path as per the project location (relative path).                                                                    pre-clean : performs tasks that are necessary prior to actual project cleaning.clean : delete all files created by the previous build.post-clean : performs tasks that are necessary to finalize project cleaning.pre-site : performs tasks that are necessary prior to actual project site generation.site : develop the project’s site generation.post-site : performs tasks that are necessary to finalize project site generation, also prepares for site deployment.site-deploy : deploy the developed site documentation to the web server of your choice.Build = TargetSource = src/main/javaTest = src/main/testjar: jar will not recompile sources; it will imply just create a JAR from the target/classes directory considering that everything else has been done.                                                                    maven-javadoc plugin is used by Maven to generate a project's javadocs. To create javadocs, this plugin internally uses the JDK\bin\javadoce.exe command. The javadocs for the project are generated when the project is deployed with the mvn install command.                                                                    -mvn archetype: create is used to start a new project. settings.xml file. It's comparable to a pom.xml file, but it's either global or user-specific. The Maven settings.xml file provides elements that define the values required to configure Maven's execution in several ways. These values include the location of the local repository, authentication information, and alternate remote repository servers among others.settings.xml file that we can change. The settings.xml file's main element, settings, can include up to nine predefined child elements :<settings xmlns = "http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
   <localRepository/>
   <interactiveMode/>
   <offline/>
   <pluginGroups/>
   <servers/>
   <mirrors/>
   <proxies/>
   <profiles/>
   <activeProfiles/>
</settings>docs, JAR files.pom"JAR.<groupId>:<artifactId>:<version>