1、到http://maven.apache.org/下载maven
2、把下载后的.zip解压到安装目录
3、设置系统的环境变量,M2_HOME和MAVEN_HOME
4、在Path路径中的maven可执行命令
5、在%MAVEN_HOME%\conf\settings.xml文件中修改maven本地仓库的位置
6、在cmd中执行mvn -version查看本机的maven配置信息,如下内容表示配置正确
7、Eclipse Luna中默认集成了maven插件,不需要额外安装,直接配置即可,指定maven的安装目录
8、指定settings.xml文件的位置,及本地仓库的位置
-Xms800m -Xmx800m -XX:PermSize=256M -XX:MaxNewSize=512m -XX:MaxPermSize=512m -Dmaven.multiModuleProjectDirectory=$M2_HOME
<?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.home}/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>D:\apache-maven-3.1.1\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> --> <server><!--正式发行仓库账号--> <id>releases</id> <username>admin</username> <password>admin123</password> </server> <server><!--快照版发行仓库账号--> <id>Snapshots</id> <username>admin</username> <password>admin123</password> </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>nexus</id> <mirrorOf>*</mirrorOf> <url>http://192.168.1.100:8080/nexus-2.7.0-06/content/groups/public/</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> --> <!-- | 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> --> <profile> <id>nexus</id> <repositories> <repository> <id>central</id> <url>http://repo1.maven.org/maven2/</url> <releases><enabled>true</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>central</id> <url>http://repo1.maven.org/maven2/</url> <releases><enabled>true</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <!-- activeProfiles | List of profiles that are active for all builds. | <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> </activeProfiles> --> <activeProfiles> <activeProfile>nexus</activeProfile> </activeProfiles> </settings>
相关推荐
Eclipse4.2_64离线配置maven3插件。不再为在线配置出错而烦恼!
SSHE示例项目是一个由Eclipse Kepler创建,Struts2.3.x+Spring3.2.x+Hibernate4.2.x+CXF2.7.x+EasyUI1.3.4+Maven架构的示例程序 当前示例演示了包括:权限控制、超大附件文件上传、EasyUI基本组件使用等等功能,具体...
maven-3.0.5安装包&eclipse-maven插件. ide:eclipse3.5以上.本人是eclipse4.2 jdk:1.6
4.2 Maven生命周期 13 4.3 Run As 15 4.4 Maven Build(compile) 16 4.5 Maven Build(package) 16 4.6 Maven Install(安装) 17 4.7 Maven Clean 18 4.8 新建Web工程 18 4.9 运行Web工程 19 5. 依赖...
Maven权威指南 Authors Tim O'Brien (Sonatype, Inc.) , John Casey (Sonatype, Inc.) , Brian Fox (Sonatype, Inc.) , Bruce Snyder () , Jason Van Zyl (Sonatype, Inc.) , Juven Xu () Abstract Maven权威指南...
Kepler创建,Struts2.3.x+Spring3.2.x+Hibernate4.2.x+CXF2.7.x+EasyUI1.3.4+Maven架构的示例程序 当前示例演示了包括:权限控制、超大附件文件上传、EasyUI基本组件使用等等功能,具体请自行看本示例演示功能 SSHE...
在Eclipse平台上完成Java后端开发实现,后端采用了MAVEN+SSM框架,在微信官方开发者平台上对小程序进行开发。Java后端主要功能是对资源进行管理,用户间依据权限不同进入不同的页面,管理员进入页面之后可以在页面对...
springframework4.2.x-src-eclipse springframework4.2.x源码,通过gradle管理生成的,经过一天探索搞出来的成果,希望后来人不用那么费劲重新来过,可直接导入eclipse neon中查看,但是要下载eclipse相关插件,...
1.3 在eclipse中构件 3 2 搭dubbo-admin、dubbo-monitor控制台 16 2.1 配置zookeeper 16 2.2 配置dubbo-admin和dubbo-monitor控制台 20 2.2.1 修改dubbo-admin配置 20 2.2.2 修改dubbo- monitor配置 20 2.2.3 启动并...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 4.2 数据库设计 3 4.2.1 数据库E/R图 3 4.2.2 数据库表 4 第五章 系统功能实现 9 5.1系统登录注册 9 5.2管理员功能模块 9 5.3用户...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 4.1数据库设计 15 4.2系统整体设计 21 4.2.1 系统设计思想 21 4.2.2系统流程图 22 5系统详细设计 23 5.1系统功能模块 23 5.2管理员...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 4.1数据库设计 12 4.2系统整体设计 21 4.2.1 系统设计思想 21 4.2.2系统流程图 21 5系统详细设计 23 5.1系统功能模块 23 5.2管理员...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 4.1数据库设计 12 4.2系统整体设计 18 4.2.1 系统设计思想 18 4.2.2系统流程图 19 5系统详细设计 21 5.1系统功能模块 21 5.2管理员...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 4.2 数据库设计 4 4.2.1 数据库E/R图 4 4.2.2 数据库表 5 第五章 系统功能实现 13 5.1系统功能模块 13 5.2后台功能模块 14 5.2.1管理...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,有偿哦,非诚勿扰! 第四章 系统设计 7 4.1功能结构 7 4.2 数据库设计 7 4.2.1 数据库E/R图 7 4.2.2 数据库表 8 第五章 系统功能实现 15 5.1管理...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 3.4 数据库设计与实现 14 3.4.1 数据库概念结构设计 14 3.4.2 数据库具体设计 16 第四章 系统功能的具体实现 21 4.1 前台功能模块 21...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 4.1功能结构 3 4.2 数据库设计 3 4.2.1 数据库E/R图 3 4.2.2 数据库表 4 第五章 系统功能实现 9 5.1系统功能模块 9 5.2后台登录 11 ...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 4.1数据库设计 16 4.2系统整体设计 22 4.2.1 系统设计思想 22 4.2.2系统流程图 22 5系统详细设计 24 5.1系统功能模块 24 5.2管理员...
Maven包:Maven3.3.9 浏览器:谷歌浏览器 支持项目二次开发和定制,非诚勿扰! 3.4数据库设计与实现 13 3.4.1数据库概念结构设计 13 3.4.2数据库具体设计 14 第四章 系统功能的具体实现 20 4.1前台功能模块 20 4.2...