前言：
JAVA开发环境的部署网上很多，本文主要是搭建eclipse+maven的开发环境，本篇算是博客开篇，以后相关demo演示将会在该环境中完成。
目录：
一、软件安装
二、代码下载
三、运行环境配置
四、注意事项总结
一、软件安装
本文用到的软件一共有以下几个：
1、jdk1.6.0_24（略）
2、apache-maven-3.0.5
要安装maven那么就先下载maven，哪里下呢，当然可以百度了，也可以点这里http://maven.apache.org/download.cgi，本人用的版本是3.0.5，其实我感觉就我的水平用哪个版本都一样，高版本那些牛B的特性怎么都用不到，下载完毕以后，请解压出来，本人放的位置是D:\develop\java\apache-maven-3.0.5，哎，学习太多语言也不是好事建个目录还要分类。
对于maven做一些配置，将bin目录加入PATH
环境变量-》系统变量-》新建MAVEN_HOME，如图：
然后在Path，最后加入%MAVEN_HOME%\bin，注意该内容与原内容的连接需要使用分号
修改maven配置文件D:\develop\java\apache-maven-3.0.5\conf\settings.xml
打开后你能看到密密麻麻的东西，其实基本不需要太关心主要做点调整就好
<?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: ~/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->
<localRepository>D:/develop/java/apache-maven-3.0.5/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>
-->
</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>
<repositories>
<repository>
<id>repo.springsource.org-release</id>
<name>springsource repository</name>
<url>http://repo.springsource.org/release</url>
</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>
其中请大家注意localRepository属性，该值代表本地仓库的位置，根据自身情况做出调整就好。
repository属性不需要修改，代表的是远程仓库的位置。
另外本人有个习惯，安装JDK的时候不怎么喜欢设置path，然后有时候又会通过命令行敲下maven的命令那么怎么办呢？需要在maven的命令行文件（D:\develop\java\apache-maven-3.0.5\bin\mvn.bat）中加上这么几句话
set JAVA_HOME=D:\Program Files\Java\jdk1.6.0_24 set MAVEN_OPTS=-Xms128m -Xmx512m -Dfile.encoding=UTF-8
这两句话，加在文件前面
测算maven是否安装成功，如图：
3、eclipse-jee-kepler-SR2-win32-x86_64
安装eclipse其实也差不多，下载软件，下载地址http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/keplersr2，然后解压就好了，这里根据自己的机器选择不同的版本就好了，kepler版本自带了maven插件这个比较方便，打开eclipse然后修改部分配置
调整默认字符集为UTF-8
保证这里的jre是我们安装的jdk
maven插件的简单配置，大功告成，然后请各位小伙伴自行安装一下SVN插件，不详细介绍了
二、代码下载
默认大家已经安装好SVN插件了，我用的是1.6版本Subclipse 1.6.x 安装地址http://subclipse.tigris.org/update_1.6.x
eclipse工具，右上角切换到“SVN资源库研究”视图
左边SVN资源库，右击新建资源库位置
需要新建地址是：http://code.taobao.org/svn/yongledemo，该地址主要保存我写的demo
检出trunk目录到本地
点击完成，指导下载结束。
三、运行环境配置
回到JAVA视图，展开下载的trunk工程目录，右击Source-》Import如图
然后工具会自动检测maven工程，检测完毕选择完成即可，
将多出一个demo工程，这个就是我们以后开发的工程。
该工程是一个标准的maven工程，war类型的工程，
一个maven工程应该怎么运行呢？我们来搞定它
新增一个maven build，参考该图做一下配置，其中jetty:run表示，使用jetty容器启动该war工程，第一次运行的时候请不要勾上offline，需要下载jetty插件包。
如果需要热部署功能，需要增加以上配置，jrebel这个工具太大了上传不了，如果需要请留言，同时修改一个配置/demo/src/main/resources/rebel.xml，可以使热部署生效
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.zeroturnaround.com"
xsi:schemaLocation="http://www.zeroturnaround.com/alderaan/rebel-2_0.xsd">
<classpath>
<dir name="D:/workspace_bak/Source-demo/demo/target/classes" />
</classpath>
<web>
<link target="/">
<dir name="D:/workspace_bak/Source-demo/demo/src/main/webapp" />
</link>
</web>
</application>
请根据自身情况修改dir路径
点击debug，启动Jerry容器，然后访问以下地址：http://127.0.0.1:8080/demo/index.html
恭喜你成功了！！！
四、注意事项总结
总结不出来，这个请大家留言补充吧~~~
时间： 2024-10-10 10:33:33