前言：
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
恭喜你成功了！！！
四、注意事項總結
總結不出來，這個請大家留言補充吧~~~