Use of maven
- Use of maven
- What is Maven?
- Maven goal
- Maven installation and configuration (Windows)
- Maven download
- set Maven environment variables
- verify
- modify configuration file
- modify local warehouse location
- modify maven's default JDK version
- add domestic mirror source
- configure Maven under Eclipse
- Attachment : Complete Settings.xml file
- Create a new maven project in Eclipse
- Add Spring environment to the maven project
- Add Spring Framework dependencies
- Add ApplicationContext.XML
What is Maven?
Apache Maven is a software project management and synthesis tool. Based on the concept of the Project Object Model (POM), Maven can manage project builds, reports and files from a central piece of information. Maven provides developers with a complete life cycle framework for building. The development team can automatically complete the basic tool construction of the project, and Maven uses a standard directory structure and default build life cycle. In multiple development team environments, Maven can be set up according to standards and complete the configuration work in a very short time. Since most project setups are simple and reusable, Maven makes developers' lives easier while creating reports, inspections, builds, and test automation setups.
Maven goals
The main goal of Maven is to provide developers with:
- The project is a comprehensive model that is reusable, easy to maintain, and easier to understand.
- Plug-ins or interactive tools, this declarative model.
The structure and content of a Maven project are declared in an XML file, pom.xml Project Object Model (POM), which is the basic unit of the entire Maven system. See the Maven POM section for details.
Maven installation and configuration (Windows)
Maven download
Download address: http://maven.apache.org/download.cgi
Download the corresponding packages for different platforms:
| system | Package names |
|---|---|
| Windows | apache-maven-3.6.3-bin.zip |
| Linux | apache-maven-3.6.3-bin.tar.gz |
| Mac | apache-maven-3.6.3-bin.tar.gz |
After downloading the package, extract it to the corresponding directory:
| system | Storage location (can be configured according to your own situation) |
|---|---|
| Windows | D:\Tools\apache-maven-3.6.3 |
| Linux | /usr/local/apache-maven-3.6.3 |
| Mac | /usr/local/apache-maven-3.6.3 |
Set Maven environment variables
Add environment variable MAVEN_HOME:
Right-click "Computer", select "Properties", then click "Advanced System Settings", click "Environment Variables" to set environment variables. The following system variables need to be configured: Create a
new system variable MAVEN_HOME, variable value: D :\Tools\apache-maven-3.6.3
Edit the system variable Path and add the variable value: %MAVEN_HOME%\bin
verify
Execute mvn –v at the command prompt, as shown below:
If you see a similar message, Apache Maven has been successfully installed on Windows.
Modify configuration file
Usually we need to modify the conf/settings.xml file in the decompression directory so that it can better suit our use.
- Note here: All modifications must be outside the comment tag, otherwise the modifications will be invalid. Many Maven tags are commented out in the examples given.
Finally, attach the entire Settings.xml file configuration example.
Modify local warehouse location
Add your own local location path inside the tag
<!-- localRepository
| The path to the local repository maven will use to store artifacts.
|
| Default: ${user.home}/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->
<localRepository>D:\Tools\maven-repository</localRepository>
Modify maven's default JDK version
Check your own JDK version:
Add a label under the label to modify maven's default JDK version.
<profile>
<id>JDK-1.8</id>
<activation>
<activeByDefault>true</activeByDefault>
<jdk>1.8</jdk>
</activation>
<properties>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
</properties>
</profile>
Add domestic mirror source
Add <mirror> under the <mirrors> tag and add the domestic mirror source, so that the jar package can be downloaded very quickly. The default central repository is sometimes even unreachable. Generally, you can use the Alibaba Cloud mirror library. Maven will start downloading from these by default, if not, it will go to the central warehouse.
<!-- 阿里云仓库 -->
<mirror>
<id>alimaven</id>
<mirrorOf>central</mirrorOf>
<name>aliyun maven</name>
<url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
</mirror>
<!-- 中央仓库1 -->
<mirror>
<id>repo1</id>
<mirrorOf>central</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo1.maven.org/maven2/</url>
</mirror>
<!-- 中央仓库2 -->
<mirror>
<id>repo2</id>
<mirrorOf>central</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo2.maven.org/maven2/</url>
</mirror>
Configure Maven under Eclipse
Eclipse itself integrates a version of Maven. But usually we use Maven that we have configured ourselves.
-
Modify the Maven used by Eclipse to your own. Click add and select your Maven installation directory. Remember to check it after adding it. Click Window ->Preferences->Maven->Installations:
-
Click UserSettings under the Maven node and modify all settings to conf/settings.xml in your own Maven directory . Click the Update Settings button, and the Local Respository below will be automatically recognized.
This completes the Maven configuration!
Attached: The complete Settings.xml file
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
| This is the configuration file for Maven. It can be specified at two levels:
|
| 1. User Level. This settings.xml file provides configuration for a single user,
| and is normally provided in ${user.home}/.m2/settings.xml.
|
| NOTE: This location can be overridden with the CLI option:
|
| -s /path/to/user/settings.xml
|
| 2. Global Level. This settings.xml file provides configuration for all Maven
| users on a machine (assuming they're all using the same Maven
| installation). It's normally provided in
| ${maven.conf}/settings.xml.
|
| NOTE: This location can be overridden with the CLI option:
|
| -gs /path/to/global/settings.xml
|
| The sections in this sample file are intended to give you a running start at
| getting the most out of your Maven installation. Where appropriate, the default
| values (values used when the setting is not specified) are provided.
|
|-->
<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 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<!-- localRepository
| The path to the local repository maven will use to store artifacts.
|
| Default: ${user.home}/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->
<localRepository>D:\Tools\maven-repository</localRepository>
<!-- interactiveMode
| This will determine whether maven prompts you when it needs input. If set to false,
| maven will use a sensible default value, perhaps based on some other setting, for
| the parameter in question.
|
| Default: true
<interactiveMode>true</interactiveMode>
-->
<!-- offline
| Determines whether maven should attempt to connect to the network when executing a build.
| This will have an effect on artifact downloads, artifact deployment, and others.
|
| Default: false
<offline>false</offline>
-->
<!-- pluginGroups
| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
|-->
<pluginGroups>
<!-- pluginGroup
| Specifies a further group identifier to use for plugin lookup.
<pluginGroup>com.your.plugins</pluginGroup>
-->
</pluginGroups>
<!-- proxies
| This is a list of proxies which can be used on this machine to connect to the network.
| Unless otherwise specified (by system property or command-line switch), the first proxy
| specification in this list marked as active will be used.
|-->
<proxies>
<!-- proxy
| Specification for one proxy, to be used in connecting to the network.
|
<proxy><id>optional</id><active>true</active><protocol>http</protocol><username>proxyuser</username><password>proxypass</password><host>proxy.host.net</host><port>80</port><nonProxyHosts>local.net|some.host.com</nonProxyHosts></proxy>
-->
</proxies>
<!-- servers
| This is a list of authentication profiles, keyed by the server-id used within the system.
| Authentication profiles can be used whenever maven must make a connection to a remote server.
|-->
<servers>
<!-- server
| Specifies the authentication information to use when connecting to a particular server, identified by
| a unique name within the system (referred to by the 'id' attribute below).
|
| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
| used together.
|
<server><id>deploymentRepo</id><username>repouser</username><password>repopwd</password></server>
-->
<!-- Another sample, using keys to authenticate.
<server><id>siteServer</id><privateKey>/path/to/private/key</privateKey><passphrase>optional; leave empty if not used.</passphrase></server>
-->
</servers>
<!-- mirrors
| This is a list of mirrors to be used in downloading artifacts from remote repositories.
|
| It works like this: a POM may declare a repository to use in resolving certain artifacts.
| However, this repository may have problems with heavy traffic at times, so people have mirrored
| it to several places.
|
| That repository definition will have a unique id, so we can create a mirror reference for that
| repository, to be used as an alternate download site. The mirror site will be the preferred
| server for that repository.
|-->
<mirrors>
<!-- mirror
| Specifies a repository mirror site to use instead of a given repository. The repository that
| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
<mirror><id>mirrorId</id><mirrorOf>repositoryId</mirrorOf><name>Human Readable Name for this Mirror.</name><url>http://my.repository.com/repo/path</url></mirror>
-->
<!-- 阿里云仓库 -->
<mirror>
<id>alimaven</id>
<mirrorOf>central</mirrorOf>
<name>aliyun maven</name>
<url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
</mirror>
<!-- 中央仓库1 -->
<mirror>
<id>repo1</id>
<mirrorOf>central</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo1.maven.org/maven2/</url>
</mirror>
<!-- 中央仓库2 -->
<mirror>
<id>repo2</id>
<mirrorOf>central</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo2.maven.org/maven2/</url>
</mirror>
</mirrors>
<!-- profiles
| This is a list of profiles which can be activated in a variety of ways, and which can modify
| the build process. Profiles provided in the settings.xml are intended to provide local machine-
| specific paths and repository locations which allow the build to work in the local environment.
|
| For example, if you have an integration testing plugin - like cactus - that needs to know where
| your Tomcat instance is installed, you can provide a variable here such that the variable is
| dereferenced during the build process to configure the cactus plugin.
|
| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
| section of this document (settings.xml) - will be discussed later. Another way essentially
| relies on the detection of a system property, either matching a particular value for the property,
| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
| Finally, the list of active profiles can be specified directly from the command line.
|
| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
| repositories, plugin repositories, and free-form properties to be used as configuration
| variables for plugins in the POM.
|
|-->
<profiles>
<!-- profile
| Specifies a set of introductions to the build process, to be activated using one or more of the
| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
| or the command line, profiles have to have an ID that is unique.
|
| An encouraged best practice for profile identification is to use a consistent naming convention
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
| This will make it more intuitive to understand what the set of introduced profiles is attempting
| to accomplish, particularly when you only have a list of profile id's for debug.
|
| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
<profile><id>jdk-1.4</id><activation><jdk>1.4</jdk></activation><repositories><repository><id>jdk14</id><name>Repository for JDK 1.4 builds</name><url>http://www.myhost.com/maven/jdk14</url><layout>default</layout><snapshotPolicy>always</snapshotPolicy></repository></repositories></profile>
-->
<profile>
<id>jdk-1.8</id>
<activation>
<jdk>1.4</jdk>
</activation>
<repositories>
<repository>
<id>jdk14</id>
<name>Repository for JDK 1.4 builds</name>
<url>http://www.myhost.com/maven/jdk14</url>
<layout>default</layout>
<snapshotPolicy>always</snapshotPolicy>
</repository>
</repositories>
</profile>
<!--
| Here is another profile, activated by the system property 'target-env' with a value of 'dev',
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration
| might hypothetically look like:
|
| ...
| <plugin>
| <groupId>org.myco.myplugins</groupId>
| <artifactId>myplugin</artifactId>
|
| <configuration>
| <tomcatLocation>${tomcatPath}</tomcatLocation>
| </configuration>
| </plugin>
| ...
|
| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
| anything, you could just leave off the <value/> inside the activation-property.
|
<profile><id>env-dev</id><activation><property><name>target-env</name><value>dev</value></property></activation><properties><tomcatPath>/path/to/tomcat/instance</tomcatPath></properties></profile>
-->
</profiles>
<!-- activeProfiles
| List of profiles that are active for all builds.
|
<activeProfiles><activeProfile>alwaysActiveProfile</activeProfile><activeProfile>anotherAlwaysActiveProfile</activeProfile></activeProfiles>
-->
</settings>
Create a new maven project in Eclipse
(1) There are additional maven-related options in the creation wizard:
(2) Select the default project location and next step
(3) Create a project and fill in the relevant groupId artifactId version and other information
Click Finish to create a simple maven project. Maven projects generally have the following structure:
pom.xml: used to define or add dependencies of jar packages
src-main: used to store java source files
src-test: used to store test cases.
target: to generate the corresponding class file or published jar package.
(4) The project just created will report an error. First configure tomcat and jdk, right-click on the project>>Build Path>>Configure Build Path.
Right-click the project's Deployment Descriptor: testmaven and select Generate Deployment Descriptor Stub
This is converted into a web project and the WEN-INF folder under webapp is generated.
(5) Continue to click Project Facets. Cancel the Dynamic Web Module option and adjust the Java, that is, JDK version to 1.8.
After clicking Apply , check Dynamic Web Module and jump its version to 3.1. The result is shown below:
If there are still errors, right-click the project's Deployment Descriptor: testmaven and select Generate Deployment Descriptor Stub
(9) Finally: If we want to set the root directory to webapp, we still right-click the project name and click Properties --> Deployment Assembly. As shown in the picture:
select this/WebContent, then click Remove, then click Add
to select Folder and click Next, then as shown in the picture: select webapp, Finish, and then Apply and Close.
Create a new jsp file under webapp,
Seeing that the above jsp page is displayed normally, it means that the web project configuration is successful.
Add Spring environment to maven project
Add Spring Framework dependency
Open the pom.xml file in the project, click the Dependencies tab, and click add to add a new dependency.
If you know the dependent group id and artifact id, you can fill them in directly. If you are not sure, you can enter keywords to query, or go to https: //mvnrepository.com/The GroupId, Artifact Id, and Version of the report that the website query relies on.
Through keyword query, modify the version number of the jar package that meets your needs.
Or query the GroupId, Artifact Id, and Version of the report you rely on through the https://mvnrepository.com/ website.
After saving, the jar package can be updated online.
Finally added the Spring jar package
AddApplicationContext.XML
Use the Spring help document to obtain the configuration file applicationContext.xml information. You can download the Spring Framework help document at
spring_framework-5.0.2.RELEASE\docs\spring-framework-reference\index.html
or use the online Spring Framework help document.
https://spring.io/projects/spring-framework#learn
Since there is no documentation for version 5.0.2 listed on Spring, we use 5.0.16 as a reference.
Click Core:
Select section 1.2.1, the content of applicationContext.xml on the right, copy it, create a new applicationContext.xml in the project src->main->resources folder, and paste the content:
Create dao and test packages under src/main/java, import TestDao.java and TestDaoImpl.java in ch1, and the test package imports Test.java.
Configure applicationContext.xml beans:
Right-click to run Test.java, Run As... and select Java Application. The following running results will appear, which means the configuration of the Spring project is completed.
Select section 1.2.1, the content of applicationContext.xml on the right, copy it, create a new applicationContext.xml in the project src->main->resources folder, and paste the content:
Create dao and test packages under src/main/java, import TestDao.java and TestDaoImpl.java in ch1, and the test package imports Test.java.
Configure applicationContext.xml beans:
Right-click to run Test.java, Run As... and select Java Application. The following running results will appear, which means the configuration of the Spring project is completed.
