【經(jīng)驗(yàn)】java項(xiàng)目開發(fā)問題總結(jié)及解決方案(更新)

1、maven項(xiàng)目在install時(shí),報(bào)錯(cuò)

  • 報(bào)錯(cuò)信息:

-Dmaven.multiModuleProjectDirectory system property is not set. Check $M2_HOME environment variable

  • 解決方案

1.添加M2_HOME的環(huán)境變量
2.Preference->Java->Installed JREs->Edit 選擇一個(gè)jdk,
添加 -Dmaven.multiModuleProjectDirectory=$M2_HOME

-Dmaven.multiModuleProjectDirectory=$M2_HOME

</br>


2、eclipse啟動(dòng)慢卡

  • 關(guān)閉不必要的啟動(dòng)項(xiàng):window——Preferences——General——Startup and Shutdown 中,把Plug-ins activated on startup下面不用的都不要勾選。
  • eclipse.ini配置文件的修改(這個(gè)應(yīng)該懂吧)。

</br>


3、用maven創(chuàng)建不了項(xiàng)目

  • 首先查看maven是否成功安裝以及配置

  • 將生成的.m2文件刪掉,再創(chuàng)建項(xiàng)目(默認(rèn)路徑一般是:C:\Users\14065.m2)

</br>


4、maven編碼gbk不可映射字符

  • 是由于Eclipse等編輯器與本地編碼格式不一致所導(dǎo)致。

安裝系統(tǒng)之后,一般中文系統(tǒng)默認(rèn)字符集是GBK。我們安裝的軟件一般都繼承使用操作系統(tǒng)的默認(rèn)字符集。所以當(dāng)在中文XP或者win7系統(tǒng)開發(fā),在使用maven(mvn compile)編譯項(xiàng)目的時(shí)候,就會(huì)出現(xiàn)“編碼 gbk 的不可映射字符”: 這個(gè)是由于代碼使用的UTF-8,而maven編譯的時(shí)候使用的GBK的緣故。 可以通過修改項(xiàng)目的pom文件,可以告訴maven這個(gè)項(xiàng)目使用UTF-8編碼來編譯。在項(xiàng)目的pom.xml文件中添加下面的配置:

 <!-- 指明編譯源代碼時(shí)使用的字符編碼,maven編譯的時(shí)候默認(rèn)使用的GBK編碼, 通過project.build.sourceEncoding屬性設(shè)置字符編碼,告訴maven這個(gè)項(xiàng)目使用UTF-8來編譯 -->  
<properties>  
  <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>  
</properties> 

</br>


5、SpringMVC項(xiàng)目運(yùn)行時(shí)找不到DispatcherServlet映射

  • 問題:

No mapping found for HTTP request with URI [/courses/view3] in DispatcherServlet with name 'mvc-dispatcher-servlet'

  • 原因一:查看對(duì)應(yīng)的配置文件 mvc-dispatcher-servlet.xml 配置的路徑是否有誤
<!-- 確保此路徑無誤 -->
<context:component-scan base-package="com.xiao.mvcdemo">
    <context:include-filter type="annotation"
            expression="org.springframework.stereotype.Controller" />
</context:component-scan>
  • 原因二:查看 web.xml 的配置是否有誤
<!-- DispatcherServlet, Spring MVC的核心 -->
  <servlet>
        <servlet-name>mvc-dispatcher</servlet-name>
        <servlet-class> org.springframework.web.servlet.DispatcherServlet</servlet-class>
        <!-- DispatcherServlet對(duì)應(yīng)的上下文配置, 默認(rèn)為/WEB-INF/$servlet-name$-servlet.xml
         -->
        <init-param>
          <param-name>contextConfigLocation</param-name>
          <param-value>/WEB-INF/configs/spring/mvc-dispatcher-servlet.xml</param-value>
        </init-param>
        <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
        <servlet-name>mvc-dispatcher</servlet-name>
        <!-- mvc-dispatcher攔截所有的請(qǐng)求-->
        <url-pattern>/</url-pattern>
</servlet-mapping>

</br>


6、如何用maven下載源代碼

  • 路徑:window——Preferences——Maven中:勾選Download Artifact Sources
Maven下載源碼

</br>


7、eclipse項(xiàng)目上初現(xiàn)紅叉

  • 將所有的jar包重新導(dǎo)入,包括tomcat、jre。

  • 可能是eclipse默認(rèn)使用的服務(wù)器不是你自己配置的,修改為自己配置的即可:右鍵項(xiàng)目——Properties——Targeted Runtimes 中選擇你自己的tomcat服務(wù)器(要仔細(xì),比如系統(tǒng)默認(rèn)的是Apache Tomcat 7,而你自己的是Tomcat 7 Server)

  • 更多類似問題參考

</br>


8、maven項(xiàng)目上有一個(gè)小紅叉

  • 報(bào)錯(cuò)信息

Description Resource Path Location Type
Project configuration is not up-to-date with pom.xml. Run project configuration update rdc line 1 Maven Configuration Problem

  • 解決方案

右鍵項(xiàng)目,【Maven】--》【Update Project Configuration...】即可

解決方案

</br>


8、普通java項(xiàng)目出現(xiàn)小紅叉

  • 解決方案

右鍵項(xiàng)目——>properties——>project facets

解決方案

右鍵項(xiàng)目——>properties——>java Compiler

解決方案

</br>


9、修改maven的本地倉庫地址

配置為自己的maven地址
配置自己的本地倉庫

</br>


10、Eclipse智能提示沒用了

  • 解決方案

    • 1、window->Preferences->Java->Editor->content assist 把 Enable auto activation 選項(xiàng)打上勾 :

      并且在點(diǎn)后面加上.abcdefghijklmnopqrstuvwxyz
      此時(shí)重啟了eclipse還不成功,之后接著第二步驟

    • 2、window->Preferences->[Java] ->Editor->Content Assist->Advanced 把該勾選的斗勾選起來

自動(dòng)提示

</br>


11、Eclipse中創(chuàng)建maven web項(xiàng)目后報(bào)錯(cuò)

  • 問題描述

web.xml is missing and <failOnMissingWebXml> is set to true

  • 解決方案

在webapp目錄下創(chuàng)建"WEB-INF",在"WEB-INF"下創(chuàng)建web.xml即可。

</br>


12、在啟動(dòng)maven項(xiàng)目時(shí),報(bào)錯(cuò)Please ensure you are using JDK 1.4 or above and not a JRE

  • 報(bào)錯(cuò)信息

Please ensure you are using JDK 1.4 or above and not a JRE

  • 報(bào)錯(cuò)原因

eclipse默認(rèn)是使用jre作為運(yùn)行環(huán)境,而maven編譯需要jdk作為運(yùn)行環(huán)境

  • 解決方案

window -> preferences -> Java -> installed jres,點(diǎn)擊add->選擇Standard VM,新加一個(gè)環(huán)境,設(shè)為默認(rèn)環(huán)境,注意location選擇為你的jdk目錄。

解決方案

如果還是不行,就在你的項(xiàng)目上右擊,build path -> configure build path,編輯JRE System Library,選擇剛才新建的默認(rèn)環(huán)境

</br>


13、tomcat啟動(dòng)maven項(xiàng)目報(bào)錯(cuò):A child container failed during start

  • 報(bào)錯(cuò)信息

嚴(yán)重: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]]
...
嚴(yán)重: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Tomcat].StandardHost[localhost]]
...

  • 報(bào)錯(cuò)原因

自己添加的 servlet.api包和tomcat的這個(gè)jar包沖突。

  • 解決方案
  • 刪掉servlet-api包
  • 在該依賴的配置中添加<scope></scope>節(jié)點(diǎn)
    <dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>servlet-api</artifactId>
    <version>2.5</version>
    <scope>provided</scope>
    </dependency>

</br>


14、maven項(xiàng)目無法加載靜態(tài)的Xml,html,tsl

  • 報(bào)錯(cuò)信息
嚴(yán)重: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'bookServiceImpl': 
Unsatisfied dependency expressed through field 'bookDao'; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'bookDao' defined in file 
[C:\Tools\develop\developer\idea\project\SSMFrame\target\classes\com\ssm\frame\dao\BookDao.class]:
 Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory';
 nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'sqlSessionFactory' defined in class path resource
 [spring/spring-dao.xml]: Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: Failed to convert property value of type 'java.lang.String' to required type 'org.springframework.core.io.Resource[]' for property 'mapperLocations'; nested exception is java.lang.IllegalArgumentException: 
Could not resolve resource location pattern [classpath:com/ssm/frame/dao/mapper/**Mapper.xml]: 
class path resource [com/ssm/frame/dao/mapper/] cannot be resolved to URL because it does not exist

Caused by: org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'bookDao' defined in file 
[C:\Tools\develop\developer\idea\project\SSMFrame\target\classes\com\ssm\frame\dao\BookDao.class]: Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-dao.xml]:Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: Failed to convert property value of type 'java.lang.String' to required type 'org.springframework.core.io.Resource[]' for property 'mapperLocations'; 
nested exception is java.lang.IllegalArgumentException: Could not resolve resource location pattern [classpath:com/ssm/frame/dao/mapper/**Mapper.xml]:
 class path resource [com/ssm/frame/dao/mapper/] cannot be resolved to URL because it does not exist

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-dao.xml]: Initialization of bean failed;nested exception is org.springframework.beans.TypeMismatchException: Failed to convert property value of type 'java.lang.String' to required type 'org.springframework.core.io.Resource[]' for property 'mapperLocations'; nested exception is java.lang.IllegalArgumentException: Could not resolve resource location pattern [classpath:com/ssm/frame/dao/mapper/**Mapper.xml]: 
class path resource [com/ssm/frame/dao/mapper/] cannot be resolved to URL because it does not exist

Caused by: org.springframework.beans.TypeMismatchException: Failed to convert property value of type 'java.lang.String' to required type 'org.springframework.core.io.Resource[]' for property 'mapperLocations'; 
nested exception is java.lang.IllegalArgumentException: Could not resolve resource location pattern [classpath:com/ssm/frame/dao/mapper/**Mapper.xml]: class path resource [com/ssm/frame/dao/mapper/] cannot be resolved to URL because it does not exist

Caused by: java.lang.IllegalArgumentException: Could not resolve resource location pattern [classpath:com/ssm/frame/dao/mapper/**Mapper.xml]: class path resource [com/ssm/frame/dao/mapper/] cannot be resolved to URL because it does not exist

  • 錯(cuò)誤分析
  • 此時(shí),你可以去項(xiàng)目的工作空間里看看,你會(huì)驚訝的發(fā)現(xiàn)并沒有生成 .xml等文件,或者生成的.class,文件并不是和你編寫的.xml、.java源文件的文件內(nèi)容一致的,有可能你新加的一些方法或參數(shù)都不在其中,比如:我的BookEntityMapper.xml文件中的pojo引用為"com.ssm.frame.entity.BookEntity",但是在生成的BookEntityMapper.class文件中是"com.ssm.frame.entity.Book"等錯(cuò)誤。
  • 是因?yàn)槟闶怯玫氖莔aven項(xiàng)目,maven項(xiàng)目都是依賴于jar配置,即依賴于pom.xml的配置,它不會(huì)自動(dòng)的為你加載靜態(tài).Xml,html,tsl 等文件,所以導(dǎo)致無法生成相應(yīng)的.class文件。
  • 解決方案
<!--在pom.xml的build節(jié)點(diǎn)中加入以下配置-->
<resources>
            <resource>
                <directory>src/main/resources</directory>
                <includes>
                    <include>**/*.properties</include>
                    <include>**/*.xml</include>
                    <include>**/*.tld</include>
                    <include>**/*.jsp</include>
                </includes>
                <filtering>true</filtering>
            </resource>

            <resource>
                <directory>src/main/java</directory>
                <includes>
                    <include>**/*.properties</include>
                    <include>**/*.xml</include>
                    <include>**/*.tld</include>
                </includes>
                <filtering>true</filtering>
            </resource>
</resources>

</br>


15、Spring加載時(shí)報(bào)錯(cuò): org.springframework.beans.factory.UnsatisfiedDependencyException

  • 報(bào)錯(cuò)信息
org.springframework.beans.factory.UnsatisfiedDependencyException
  • 錯(cuò)誤分析

Spring 的自動(dòng)注入所依賴的jar包,缺少任何一個(gè)都無法成功通過Spring進(jìn)行注入

  • 解決方案

        <dependency>
            <groupId>org.aspectj</groupId>
            <artifactId>aspectjrt</artifactId>
            <version>1.6.12</version>
        </dependency>
        <dependency>
            <groupId>aspectj</groupId>
            <artifactId>aspectjweaver</artifactId>
            <version>1.5.3</version>
        </dependency>

</br>


16、springMVC項(xiàng)目啟動(dòng)時(shí)JNDI NameNotFoundException

  • 錯(cuò)誤信息
 [org.springframework.jndi.JndiLocatorDelegate] - Converted JNDI name [java:comp/env/spring.liveBeansView.mbeanDomain] not found - trying original name [spring.liveBeansView.mbeanDomain]. javax.naming.NameNotFoundException:
  • 解決方案
<!-- 在web.xml中添加 -->
<context-param>
        <param-name>spring.profiles.active</param-name>
        <param-value>dev</param-value>
    </context-param>
    <context-param>
        <param-name>spring.profiles.default</param-name>
        <param-value>dev</param-value>
    </context-param>
    <context-param>
        <param-name>spring.liveBeansView.mbeanDomain</param-name>
        <param-value>dev</param-value>
    </context-param>

</br>


17、當(dāng)數(shù)據(jù)庫中時(shí)間為“0000-00-00 00:00:00”時(shí),加載到頁面時(shí)報(bào)錯(cuò)

  • 解決方案
 jdbc.url=jdbc:mysql://localhost:3306/ssm?useUnicode=true&characterEncoding=utf-8&zeroDateTimeBehavior=convertToNull&useSSL=false

<!-- zeroDateTimeBehavior=convertToNull -->

18、通過maven搭建的javaweb項(xiàng)目pom文件報(bào)錯(cuò)

  • 錯(cuò)誤信息
Execution default-resources of goal org.apache.maven.plugins:maven-resources-plugin:2.6:resources failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-resources-plugin:2.6:resources: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.sonatype.plexus.build.incremental.BuildContext.newScanner(Ljava/io/File;Z)Lorg/codehaus/plexus/util/Scanner;" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/apache/maven/shared/filtering/DefaultMavenResourcesFiltering, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/sonatype/plexus/build/incremental/BuildContext, have different Class objects for the type org/codehaus/plexus/util/Scanner used in the signature
-----------------------------------------------------
realm =    plugin>org.apache.maven.plugins:maven-resources-plugin:2.6
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] = file:/C:/Develop/Tools/Maven/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar
urls[1] = file:/C:/Develop/Tools/Maven/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
urls[2] = file:/C:/Develop/Tools/Maven/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
urls[3] = file:/C:/Develop/Tools/Maven/.m2/repository/org/apache/maven/shared/maven-filtering/1.1/maven-filtering-1.1.jar
urls[4] = file:/C:/Develop/Tools/Maven/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.13/plexus-interpolation-1.13.jar
Number of foreign imports: 1
import: Entry[import  from realm ClassRealm[maven.api, parent: null]]

-----------------------------------------------------
 (org.apache.maven.plugins:maven-resources-plugin:2.6:resources:default-resources:process-resources)

org.apache.maven.plugin.PluginExecutionException: Execution default-resources of goal org.apache.maven.plugins:maven-resources-plugin:2.6:resources failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-resources-plugin:2.6:resources: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.sonatype.plexus.build.incremental.BuildContext.newScanner(Ljava/io/File;Z)Lorg/codehaus/plexus/util/Scanner;" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/apache/maven/shared/filtering/DefaultMavenResourcesFiltering, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/sonatype/plexus/build/incremental/BuildContext, have different Class objects for the type org/codehaus/plexus/util/Scanner used in the signature
-----------------------------------------------------
realm =    plugin>org.apache.maven.plugins:maven-resources-plugin:2.6
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] = file:/C:/Develop/Tools/Maven/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar
urls[1] = file:/C:/Develop/Tools/Maven/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
urls[2] = file:/C:/Develop/Tools/Maven/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
urls[3] = file:/C:/Develop/Tools/Maven/.m2/repository/org/apache/maven/shared/maven-filtering/1.1/maven-filtering-1.1.jar
urls[4] = file:/C:/Develop/Tools/Maven/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.13/plexus-interpolation-1.13.jar
Number of foreign imports: 1
import: Entry[import  from realm ClassRealm[maven.api, parent: null]]

-----------------------------------------------------

    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:183)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
    at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
    at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: org.apache.maven.plugin.PluginContainerException: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-resources-plugin:2.6:resources: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.sonatype.plexus.build.incremental.BuildContext.newScanner(Ljava/io/File;Z)Lorg/codehaus/plexus/util/Scanner;" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/apache/maven/shared/filtering/DefaultMavenResourcesFiltering, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/sonatype/plexus/build/incremental/BuildContext, have different Class objects for the type org/codehaus/plexus/util/Scanner used in the signature
-----------------------------------------------------
realm =    plugin>org.apache.maven.plugins:maven-resources-plugin:2.6
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] = file:/C:/Develop/Tools/Maven/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar
urls[1] = file:/C:/Develop/Tools/Maven/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
urls[2] = file:/C:/Develop/Tools/Maven/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
urls[3] = file:/C:/Develop/Tools/Maven/.m2/repository/org/apache/maven/shared/maven-filtering/1.1/maven-filtering-1.1.jar
urls[4] = file:/C:/Develop/Tools/Maven/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.13/plexus-interpolation-1.13.jar
Number of foreign imports: 1
import: Entry[import  from realm ClassRealm[maven.api, parent: null]]

-----------------------------------------------------

    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:181)
    ... 31 more
Caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.sonatype.plexus.build.incremental.BuildContext.newScanner(Ljava/io/File;Z)Lorg/codehaus/plexus/util/Scanner;" the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class, org/apache/maven/shared/filtering/DefaultMavenResourcesFiltering, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/sonatype/plexus/build/incremental/BuildContext, have different Class objects for the type org/codehaus/plexus/util/Scanner used in the signature
    at org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(DefaultMavenResourcesFiltering.java:221)
    at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:301)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    ... 31 more
  • 解決方案

在pom.xml中添加maven-resources-plugin配置項(xiàng)

    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
             <!-- 添加信息 -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-resources-plugin</artifactId>
                <version>2.4.3</version>
            </plugin>

        </plugins>
    </build>
最后編輯于
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請(qǐng)聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成,瀏覽時(shí)請(qǐng)結(jié)合常識(shí)與多方信息審慎甄別。
平臺(tái)聲明:文章內(nèi)容(如有圖片或視頻亦包括在內(nèi))由作者上傳并發(fā)布,文章內(nèi)容僅代表作者本人觀點(diǎn),簡(jiǎn)書系信息發(fā)布平臺(tái),僅提供信息存儲(chǔ)服務(wù)。

相關(guān)閱讀更多精彩內(nèi)容

  • Spring Boot 參考指南 介紹 轉(zhuǎn)載自:https://www.gitbook.com/book/qbgb...
    毛宇鵬閱讀 47,253評(píng)論 6 342
  • Spring Cloud為開發(fā)人員提供了快速構(gòu)建分布式系統(tǒng)中一些常見模式的工具(例如配置管理,服務(wù)發(fā)現(xiàn),斷路器,智...
    卡卡羅2017閱讀 136,506評(píng)論 19 139
  • 1. Java基礎(chǔ)部分 基礎(chǔ)部分的順序:基本語法,類相關(guān)的語法,內(nèi)部類的語法,繼承相關(guān)的語法,異常的語法,線程的語...
    子非魚_t_閱讀 34,623評(píng)論 18 399
  • 轉(zhuǎn)自陳明乾的博客,可能有一定更新。 轉(zhuǎn)原文聲明:原創(chuàng)作品,允許轉(zhuǎn)載,轉(zhuǎn)載時(shí)請(qǐng)務(wù)必以超鏈接形式標(biāo)明文章 原始出處 、...
    C86guli閱讀 4,865評(píng)論 6 72
  • 撫一曲 眉間宇心 描一幅 青衫琉璃 縱星辰萬里 青絲拂指如縷 攜清風(fēng)與你 為江山伏筆 我愿...
    于典閱讀 474評(píng)論 0 1

友情鏈接更多精彩內(nèi)容