Maven用法

来源：互联网发布：雄猫软件编辑：程序博客网时间：2024/06/04 00:23

1. 下载apache-maven-3.2.5

2. 配置mavne环境变量

测试maven环境变量配置

3. Eclipse与maven建立关联

4. Settings.xml配置【配置本地仓库】

<?xmlversion="1.0" encoding="UTF-8"?>

<!--

Licensedto the Apache Software Foundation (ASF) under one

or morecontributor license agreements. See theNOTICE file

distributedwith this work for additional information

regardingcopyright ownership. The ASF licensesthis file

to youunder the Apache License, Version 2.0 (the

"License");you may not use this file except in compliance

with theLicense. You may obtain a copy of theLicense at

http://www.apache.org/licenses/LICENSE-2.0

Unlessrequired by applicable law or agreed to in writing,

softwaredistributed under the License is distributed on an

"ASIS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY

KIND,either express or implied. See theLicense for the

specificlanguage governing permissions and limitations

under theLicense.

-->

<!--

| This is the configuration file for Maven. Itcan 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 beoverridden 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 (assumingthey're all using the same Maven

| installation). It's normallyprovided in

| ${maven.home}/conf/settings.xml.

| NOTE: This location can beoverridden with the CLI option:

| -gs/path/to/global/settings.xml

| The sections in this sample file are intendedto give you a running start at

| getting the most out of your Maveninstallation. Where appropriate, the default

| values (values used when the setting is notspecified) are provided.

|-->

<settingsxmlns="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.0http://maven.apache.org/xsd/settings-1.0.0.xsd">

<!-- localRepository

| The path to the local repository mavenwill use to store artifacts.

| Default: ${user.home}/.m2/repository

<localRepository>/path/to/local/repo</localRepository>

-->

<localRepository>C:/Users/youyidong/.m2/repository</localRepository>

<!-- interactiveMode

| This will determine whether maven promptsyou 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

-->

<!-- offline

| Determines whether maven should attempt toconnect to the network when executing a build.

| This will have an effect on artifactdownloads, artifact deployment, and others.

| Default: false

<offline>false</offline>

-->

<!-- pluginGroups

| This is a list of additional groupidentifiers 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.

|-->

<!-- pluginGroup

| Specifies a further group identifier touse for plugin lookup.

<pluginGroup>com.your.plugins</pluginGroup>

-->

</pluginGroups>

<!-- proxies

| This is a list of proxies which can beused on this machine to connect to the network.

| Unless otherwise specified (by systemproperty or command-line switch), the first proxy

| specification in this list marked asactive will be used.

|-->

<!-- proxy

| Specification for one proxy, to be usedin connecting to the network.

<proxy>

<id>optional</id>

<username>proxyuser</username>

<password>proxypass</password>

<host>proxy.host.net</host>

<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 usedwhenever maven must make a connection to a remote server.

|-->

<!-- server

| Specifies the authentication informationto 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 specifyusername/password OR privateKey/passphrase, since these pairings are

| used together.

<id>deploymentRepo</id>

<username>repouser</username>

<password>repopwd</password>

</server>

-->

<!-- Another sample, using keys toauthenticate.

<id>siteServer</id>

<privateKey>/path/to/private/key</privateKey>

<passphrase>optional; leave emptyif not used.</passphrase>

</server>

-->

</servers>

<!-- mirrors

| This is a list of mirrors to be used indownloading artifacts from remote repositories.

| It works like this: a POM may declare arepository to use in resolving certain artifacts.

| However, this repository may have problemswith heavy traffic at times, so people have mirrored

| it to several places.

| That repository definition will have aunique id, so we can create a mirror reference for that

| repository, to be used as an alternatedownload site. The mirror site will be the preferred

| server for that repository.

|-->

<!-- mirror

| Specifies a repository mirror site touse instead of a given repository. The repository that

| this mirror serves has an ID thatmatches the mirrorOf element of this mirror. IDs are used

| for inheritance and direct lookuppurposes, and must be unique across the set of mirrors.

|-->

<id>mirrorId</id>

<mirrorOf>repositoryId</mirrorOf>

<name>Human Readable Name for thisMirror.</name>

<url>http://mvnrepository.com</url>

</mirror>

</mirrors>

<!-- profiles

| This is a list of profiles which can beactivated in a variety of ways, and which can modify

| the build process. Profiles provided inthe settings.xml are intended to provide local machine-

| specific paths and repository locationswhich allow the build to work in the local environment.

| For example, if you have an integrationtesting plugin - like cactus - that needs to know where

| your Tomcat instance is installed, you canprovide a variable here such that the variable is

| dereferenced during the build process toconfigure the cactus plugin.

| As noted above, profiles can be activatedin 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 systemproperty, either matching a particular value for the property,

| or merely testing its existence. Profilescan also be activated by JDK version prefix, where a

| value of '1.4' might activate a profilewhen the build is executed on a JDK version of '1.4.2_07'.

| Finally, the list of active profiles canbe specified directly from the command line.

| NOTE: For profiles defined in thesettings.xml, you are restricted to specifying only artifact

| repositories, plugin repositories, and free-form properties to be usedas configuration

| variables for plugins in the POM.

|-->

<!-- profile

| Specifies a set of introductions to thebuild process, to be activated using one or more of the

| mechanisms described above. Forinheritance purposes, and to activate profiles via <activatedProfiles/>

| or the command line, profiles have tohave an ID that is unique.

| An encouraged best practice for profileidentification 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 tounderstand what the set of introduced profiles is attempting

| to accomplish, particularly when you onlyhave a list of profile id's for debug.

| This profile example uses the JDKversion to trigger activation, and provides a JDK-specific repo.

</activation>

<name>Repository for JDK 1.4builds</name>

<url>http://www.myhost.com/maven/jdk14</url>

<layout>default</layout>

<snapshotPolicy>always</snapshotPolicy>

</repository>

</repositories>

</profile>

-->

<!--

| Here is another profile, activated bythe system property 'target-env' with a value of 'dev',

| which provides a specific path to theTomcat 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 thisconfiguration whenever someone set 'target-env' to

| anything, you could just leave off the <value/> inside theactivation-property.

<name>target-env</name>

</property>

</activation>

<tomcatPath>/path/to/tomcat/instance</tomcatPath>

</properties>

</profile>

-->

</profiles>

<!-- activeProfiles

| List of profiles that are active for allbuilds.

<activeProfile>alwaysActiveProfile</activeProfile>

<activeProfile>anotherAlwaysActiveProfile</activeProfile>

</activeProfiles>

-->

</settings>

5. maven项目中配置远程仓库【maven项目的pom.xml文件】

<projectxmlns="http://maven.apache.org/POM/4.0.0"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0http://maven.apache.org/maven-v4_0_0.xsd">

<groupId>com.shunhe</groupId>

<version>0.0.1-SNAPSHOT</version>

<name>coreMaven Webapp</name>

<url>http://maven.apache.org</url>

<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

<maven.build.timestamp.format>yyyy-MM-dd HH:mm:ss</maven.build.timestamp.format>

<jdk.version>1.7</jdk.version>

<spring.version>3.2.8.RELEASE</spring.version>

<hibernate.version>3.5.5-Final</hibernate.version>

<CKFinder.version>2.4</CKFinder.version>

<spring.security.version>3.2.5.RELEASE</spring.security.version>

</properties>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

</dependency>

<groupId>org.springframework</groupId>

<artifactId>spring-context</artifactId>