Maven的bug：构建桌面上的工程时报错？

    今天发现Maven的一个有趣的现象，不是这算不算是Maven的bug，大家也说说看。
     我在桌面上用Eclipse建了一个工程，然后用maven构建，老是报如下异常：

C:\Documents and Settings\liu_hliang\桌面\loong-deploycommand>mvn clean install
C:\Documents and Settings\liu_hliang\桌面\loong-deploycommand>set MAVEN_OPTS= -Xms128m -Xmx512m
[INFO] Scanning for projects...
[INFO] ---------------------------------------------------------------[ERROR] FATAL ERROR
[INFO] ---------------------------------------------------------------[INFO] Error building POM (may not be this project's POM).

Project ID: org.trustie.loong.modules.loong-deployment:loong-deploycommand
POM Location: C:\Documents and Settings\liu_hliang\桌面\pom.xml

Reason: Parse error reading POM. Reason: end tag name </project> must match start tag name <dependencies> from line 58 (position: TEXT seen ...<dependencies>\t\t\r\n</project>... @59:11)  for proj

[INFO] ---------------------------------------------------------------[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. Reason: end tag name </project> must match start tag name <dependencies> from line 58 (position: TEXT seen ...<dependenci
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error reading POM. Reason: end tag name </project> must match start tag name <dependencies> from line 58 (position: TEXT see
        at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1592)
        at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1553)
        at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1294)
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
        at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
        at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
        at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
        ... 11 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name </project> must match start tag name <dependencies> from line 58 (position: TEXT seen ...<dependencies>\t\t\r\n</p
        at org.codehaus.plexus.util.xml.pull.MXParser.parseEndTag(MXParser.java:1689)
        at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1131)
        at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1093)
        at org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:1061)
        at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2327)
        at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4422)
        at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1588)
        ... 19 more
[INFO] ---------------------------------------------------------------[INFO] Total time: < 1 second
[INFO] Finished at: Fri Sep 04 14:21:32 CST 2009
[INFO] Final Memory: 1M/127M
[INFO] ---------------------------------------------------------------
C:\Documents and Settings\liu_hliang\桌面\loong-deploycommand>

    我后来又仔细检查了自己的pom文件，没发现有任何问题，重复几次后，问题依旧。最后我把项目移到了E盘中，结果构建成功！
    后来我又试了其它的项目，发现以前能成功构建的项目放到桌面上后都报和上述一摸一样的异常，大家知道是为什么吗？
    附：我的开发环境设置：
     操作系统：windows xp
    JDK:   1.5.12
    Maven：2.0.9

评论

6 楼 yhgstudy 2014-02-12  

去所在的workspace下面的.metadata\.plugins\org.eclipse.core.resources\.projects下把多的项目删除掉就可以了

5 楼 ferreousbox 2010-05-21  

我的问题也解决了，原来是类的注释中有中文的问题，汗一个，估计是不支持中文导致解析XML失败，具体的请看我这篇blog
http://ferreousbox.iteye.com/blog/671466

4 楼 ferreousbox 2010-05-21  

我的也存在同样的问题，找了半天不知道什么问题，完全按照官方的文档来弄的，而且我的pom文件中也没有你的relativepath这样的设置，路径中也没有空格、中文，但就是不成功，我都郁闷死了

3 楼 liu_hliang 2009-09-07  

问题解决了：在我的工程里pom文件中有如下设置：

<parent>
    <groupId>org.trustie.loong.modules.loong-deployment</groupId>
    <artifactId>loong-deployment</artifactId>
    <version>0.1.0-SNAPSHOT</version>
    <relativePath>../pom.xml</relativePath>
</parent>

   
    原因就是上面的

引用

relativePath

指定了父工程的pom文件位置，而碰巧的是我的桌面上正好有个有错的pom文件 

2 楼 liu_hliang 2009-09-07  

不是中文的问题，也不是路径中含有空格的问题，我都试过，症状依旧！

1 楼 yyc_it 2009-09-07  

是不是目录含有中文？？