Eclipse下Maven新建項目、自動打依賴jar包（包含普通項目和Web項目）

 

　　不多說，直接上干貨！

 

 

 

　　當我們無法從本地倉庫找到需要的構件的時候，就會從遠程倉庫下載構件至本地倉庫。一般地，對於每個人來說，書房只有一個，但外面的書店有很多，類似第，對於Maven來說，每個用戶只有一個本地倉庫，但可以配置訪問很多遠程倉庫。

 

 

Eclipse *版本

Eclipse *下載

 

強烈推薦書籍：Maven實戰   許曉斌著。目前是第一版 

 

注意：最新版本的Eclipse代號Mars，已經直接集成了Maven，所以無需安裝m2Eclipse插件。

 

 

 

Eclipse下新建Maven項目

1、下載Maven安裝包

　　進入Maven官網的下載頁面：http://maven.apache.org/download.cgi，如下圖所示：

 

 

 

　　選擇當前最新版本："apache-maven-3.3.9-bin.zip"，下載到本地，解壓縮到本地磁盤下。

 

 

2、配置

　　 2.1 環境變量的配置

 

 

 

 

 

2.2 修改默認的本地倉庫位置

　　進入Maven安裝目錄下的conf子目錄中，打開settings.xml進行配置修改。

 　　

 

<!-- 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:/SoftWare/maven/repository</localRepository>

 

 

　　Maven默認的本地倉庫位置是當前用戶工作目錄下的".m2/repository"，使用過程中這個目錄里的文件會比較多，占用空間越來越大。一般建議更換到其它磁盤目錄下。如下配置，就把默認的本地倉庫更改到自己創建的目錄。

　　如下圖所示的localRepository標簽中設置，就把默認的本地倉庫更改到D:/SoftWare/maven/repository這個目錄(這個目錄結構需要自己創建好)。

 

 

 

 

 

 

 2.3修改默認的中央倉庫鏡像

　　Maven默認的中央倉庫里的文件不全。所以，都需要自行添加其它的鏡像地址。在settings.xml文件中的“<mirrors>”標簽里添加如下內容：

 

 

 

 

　　其實，是如下   http://mirrors.ibiblio.org/maven2/

 

 

 

 

　注意啦！有時候，上面這樣配置，不穩定，我這里給大家分享一個穩定的setting.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: ${user.home}/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->

<localRepository>D:/SoftWare/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>osc</id>
<mirrorOf>central</mirrorOf>
<url>http://maven.aliyun.com/nexus/content/repositories/central</url>
</mirror>

<mirror>
<id>osc_thirdparty</id>
<mirrorOf>thirdparty</mirrorOf>
<url>http://maven.aliyun.com/nexus/content/repositories/central</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>jdk-1.4</id>
<activation>
<jdk>1.4</jdk>
</activation>

<repositories>

<repository>
<id>nexus</id>
<name>local private nexus</name>
<url>http://maven.aliyun.com/nexus/content/repositories/central</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>

</repositories>

<pluginRepositories>

<pluginRepository>
<id>nexus</id>
<name>local private nexus</name>
<url>http://maven.aliyun.com/nexus/content/repositories/central</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>

</pluginRepositories>
</profile>

<profile>
<id>osc</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>

<repositories>

<repository>
<id>osc</id>
<url>http://maven.aliyun.com/nexus/content/repositories/central</url>
</repository>

<repository>
<id>osc_thirdparty</id>
<url>http://maven.aliyun.com/nexus/content/repositories/central</url>
</repository>

</repositories>

<pluginRepositories>

<pluginRepository>
<id>osc</id>
<url>http://maven.aliyun.com/nexus/content/repositories/central</url>
</pluginRepository>

</pluginRepositories>
</profile>
</profiles>

<!-- activeProfiles
| List of profiles that are active for all builds.
|
<activeProfiles>
<activeProfile>alwaysActiveProfile</activeProfile>
<activeProfile>anotherAlwaysActiveProfile</activeProfile>
</activeProfiles>
-->
</settings>

 

 

　　保存所做的修改，同時還需要把這個settings.xml文件復制一份到“D:\SoftWare\maven”目錄下。

 

 

 

 

3、eclipse里的Maven插件安裝

　　Eclipse默認不支持Maven。需要給它添加m2eclipse插件。下面是具體的操作步驟。

3.1、插件安裝

　　打開Eclipse的Help->Install New Software,如下圖所示：

 

 

 

　　選擇“Add..”按鈕，又會彈出如下對話框：

 

     這個對話框就是用於添加一個插件地址的。在“Name”對應的輸入框里輸入該操作的一個標識名。在“Location”對應的輸入框里輸入這個插件的安裝地址。注：Maven的Eclipse插件地址為：http://download.eclipse.org/technology/m2e/releases。輸入后，如下圖所示：

Name:  m2e

Location:  http://download.eclipse.org/technology/m2e/releases

 

 

 

　　輸入完成后，點擊右下角的“OK”按鈕，就會彈出如下對話框：

　　MARS版本

 

 

　　我這里，就，已經安裝過了。

 

　　這一步，有可能會

注意：安裝maven時一定要注意版本匹配問題：下面就是我安裝時遇到的問題

首先安裝maven時遇到Missing requirement: m2e logback configuration 1.7.0.20160603-1933 (org.eclipse.m2e.logback.configur。。。的問題。

這是由於eclipse和maven插件版本不匹配，我的eclipse版本為如下，只能安裝m2e - http://download.eclipse.org/technology/m2e/releases/1.3的版本,高版本就報錯

 

　　推薦用MARS版本！！！

 

 　　注意，有些版本，我已測試過，如，NEON版本

 

　　會發生上述的錯誤。

 

　　這里需要選擇想要安裝的插件的詳細內容。選中“Maven Integration for Eclipse”前面的復選框。如下圖所示：

 

　　選擇完成后，點擊右下方的“Next>”按鈕進行安裝。安裝成功后，會提示需要重啟Eclipse來生效這次配置。重啟之后，這個Eclipse就可以使用m2eclipse插件功能了。

 

 

 

 

需要一段時間

 

　　自動重啟

 

3.2、Eclipse下對maven進行配置

 　　插件安裝好之后，還需要進行一些配置才能夠開始使用Maven的功能。

3.2.1、 設置m2eclipse插件所關聯的Maven程序

　　需要修改配置：首先選擇Window->Preferences,彈出如下對話框

 

 

　　在這個對話框左邊的導航欄中展開“Maven”目錄結點，並選擇“Installations”子節點，如下圖所示：

 

　　這里需要關聯上對應的Maven安裝程序。具體操作是，在右邊面板中選擇“Add…”按鈕，會彈出如下選擇Maven安裝目錄的選擇對話框：

　　通過這個對話框來選擇Maven的具體安裝目錄。選擇好之后就點擊“確定”按鈕。如下圖所示：

 

 

 

 

3.2.2、 設置自定義的本地倉庫

 　　選擇如上圖對話窗口左邊菜單樹 “Maven”節點下的“UserSettings”子節點，它默認的配置文件是“C:\Documents and Settings\csdn\.m2\settings.xml”，如下圖所示：

 

　　這邊需要修改為我們自定義倉庫位置下的settings.xml文件。具體操作是，點擊“Browse…”按鈕來選擇上一步驟修改的本地倉庫目錄下的settings.xml文件，如下圖所示：

 

 

 

 　　在上圖中選擇D:\SoftWare\apache-maven-3.3.9\conf目錄下的“settings.xml”文件，點擊“打開”按鈕來確認剛才的選擇，就會回到如下圖的對話窗口中：

 

 

 

　　在上圖中點擊右下角的“OK”按鈕來完成所有的配置修改。

 

 

4、Eclipse創建maven項目

 　　在eclipse菜單欄中選擇"File"->"News"->"Other"菜單項，就會打開如下對話窗口，在窗口中選擇"Maven"節點下"Maven Project"條目，如下圖所示，之后跟着下一步。。。就可以將項目創建好了。

 

 

 

　　我這里，選擇other

 

　　想說的是，SBT是為scala專門而設計的，但是，一般很多人還是用的是maven。

 

 

　　使用maven-archetype-quickstart 或者 coccoon-22-archetype-webapp

　　

　　 或者

 

　　也許，這一步，會碰到如下問題。

 

解決辦法：

 

 

或者

Catalog File: http://repo2.maven.org/maven2/archetype-catalog.xml

Description: maven catalog

 

 　　然后，再重新 File  ->   New   ->   Maven Project   

 

 

 

 

 

 

　　這里，自己任意取，

　　Group Id:  com.zhouls.spark

　　Artifact Id:  SparkApps

 

 

　

　　CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-compiler-plugin:3.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-compiler-plugin:jar:3.1: UnresolvableModelException: Failure to transfer org.apache.maven.plugins:maven-plugins:pom:24 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-plugins:pom:24 from/to central (https://repo.maven.apache.org/maven2): timeout

 

解決方法：

　　1.找到maven庫目錄，進入：D:\SoftWare\maven\repository\org\apache\maven\plugins\maven-compiler-plugin\3.1

 

　　2. 若3.1這個目錄下只有，"maven-compiler-plugin-3.1.pom.lastUpdated" 則需要到http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/3.1/，把里面的文件下載下來放到目錄3.1下，如果該倉庫中沒有，那么可以去http://search.maven.org/這個地方下載下來，然后放置到對應的本地倉庫中

　　可見，我這里是不需進行步驟2，直接到步驟3.

 

3.刪除3.1下的maven-compiler-plugin-3.1.pom.lastUpdated文件或3.1目錄下的所有文件

 

 

 

 

4.項目右鍵-->maven-->Update Dependencies

 

 即，得到解決！

如果以上方法還是無法解決該問題：則 打開settings.xml，嘗試換個mirror鏡像或者干脆采用默認的倉庫,即注釋掉

 

 

 

 

　　刪除清空

 

 

　　再重新來一次

 

 

 

 

這里，我繼續，上面的步驟，下來。用了我那個穩定的setting.xml文件，之后，中間不會出現什么問題！！！

 

 

 

　　把此處默認的jdk，J2SE-1.5，變成我們自己安裝的jdk版本（jdk1.7或jdk1.8）

 

 

 

 

　　得到

 　　對應，得到

 

 

　　這個pom.xml文件，里有我們工程實際時編寫和運行時的依賴和支持。

　　進入，如下

 

 

 

　　選擇，pom.xml

 

 

　　在修改pom.xml文件之前，Maven Dependencies如下

 

　　創建項目之后，pom.xml默認的內容如下

<project xmlns="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.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>

<groupId>com.zhouls.spark</groupId>
<artifactId>SparkApps</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

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

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

<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>

 

 

 

　　這一步，最為關鍵，具體怎么修改pom.xml，是要看自己的需求。

    http://mvnrepository.com/ 

 

　　我這里，因為是spark1.5.2版本。

 

 

 

 

 

 

　　其他的，類似，這里不多贅述。

轉】maven核心，pom.xml詳解

 

　　在這過程中，最好是去復制，官網。為了避免自己手誤或者格式不對！！！可以避免如下面的錯誤！

 

修改后的pom.xml內容是

 

<project xmlns="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.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>

<groupId>com.zhouls.spark</groupId>
<artifactId>SparkApps</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

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

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<junit.version>4.10</junit.version>
<spark.version>1.5.2</spark.version>
<hadoop.version>2.6.0</hadoop.version>
</properties>

<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-core_2.10</artifactId>
<version>${spark.version}</version>
</dependency>
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-sql_2.10</artifactId>
<version>${spark.version}</version>
</dependency>
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-hive_2.10</artifactId>
<version>${spark.version}</version>
</dependency>
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-streaming_2.10</artifactId>
<version>${spark.version}</version>
</dependency>
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-streaming-kafka_2.10</artifactId>
<version>${spark.version}</version>
</dependency>
<dependency>
<groupId>org.apache.hadoop</groupId>
<artifactId>hadoop-client</artifactId>
<version>${hadoop.version}</version>
</dependency>
</dependencies>

<build>
<sourceDirectory>src/main/java</sourceDirectory>
<testSourceDirectory>src/main/test</testSourceDirectory>

<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
<archive>
<manifest>
<mainClass></mainClass>
</manifest>
</archive>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.2.1</version>
<executions>
<execution>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
<configuration>
<executable>java</executable>
<includeProjectDependencies>true</includeProjectDependencies>
<includePluginDependencies>false</includePluginDependencies>
<classpathScope>compile</classpathScope>
<mainClass>com.zhouls.spark.SparkApps.cores.WordCount</mainClass>
</configuration>
</plugin>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target> 
</configuration> 
</plugin>

</plugins>
</build>
</project>

 

 

 

 

 

　　正在下載

 

 

　　立馬生成好了。可見，Maven自動生成jar包，多么的方便！

 

 

　　其他的一一去解決！

 

　　對應地，生成，

 

 

 

 　　我的這里，得到如下

 

 　　至此，Eclipse下新建Maven項目、自動打依賴jar包。大功告成！！！

 

 

 

 Eclipse里創建Maven，比較有價值的錯誤總結

http://blog.csdn.net/afgasdg/article/details/12757433

http://blog.csdn.net/sunnylinner/article/details/52183156

http://www.cnblogs.com/liaojie970/p/5509760.html 

http://www.cnblogs.com/tenghoo/p/maven_error.html   

 

 

 

　　感謝如下博主：

http://www.cnblogs.com/ljdblog/p/5840858.html

http://blog.csdn.net/qjyong/article/details/9098213

http://dead-knight.iteye.com/blog/1910783 

 

 

關於Maven的進一步，深入學習，推薦

 

 

 

 

 

 

 

 

 

 

 

 

歡迎大家，加入我的微信公眾號：大數據躺過的坑        人工智能躺過的坑

 

 

 

同時，大家可以關注我的個人博客：

   http://www.cnblogs.com/zlslch/   和     http://www.cnblogs.com/lchzls/      http://www.cnblogs.com/sunnyDream/   

   詳情請見：http://www.cnblogs.com/zlslch/p/7473861.html

 

　　人生苦短，我願分享。本公眾號將秉持活到老學到老學習無休止的交流分享開源精神，匯聚於互聯網和個人學習工作的精華干貨知識，一切來於互聯網，反饋回互聯網。
　　目前研究領域：大數據、機器學習、深度學習、人工智能、數據挖掘、數據分析。 語言涉及：Java、Scala、Python、Shell、Linux等 。同時還涉及平常所使用的手機、電腦和互聯網上的使用技巧、問題和實用軟件。 只要你一直關注和呆在群里，每天必須有收獲

 

      對應本平台的討論和答疑QQ群：大數據和人工智能躺過的坑（總群）（161156071）