2014-04-15 41 views
2

我有Java应用程序,这是由Maven的3.0.3建(MAVEN_OPTS = -Xms256m -Xmx2g -XX:MaxPermSize参数=512米)。的Maven - 添加具有不同的分类相同的依赖导致的OutOfMemoryError

在pom.xml文件我有依赖于另一个组件:

<dependency> 
    <groupId>org.component</groupId> 
    <artifactId>component-core</artifactId> 
    <version>component.110</version> 
<dependency> 

我想用一些类从这个组件,它被打包为测试:

<dependency> 
    <groupId>org.component</groupId> 
    <artifactId>component-core</artifactId> 
    <version>component.110</version> 
    <classifier>tests</classifier> 
    <scope>test</scope> 
</dependency> 

加入后这种依赖我不能编译我的应用程序,因为:

[ERROR] Java heap space -> [Help 1] 
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 
[ERROR] Re-run Maven using the -X switch to enable full debug logging. 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles: 
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError 

当我只使用主d依赖或唯一测试分类器依赖项一切正在编译和工作。我怎样才能使用他们?

我将不胜感激任何帮助。

最好的问候, 克里斯

编辑:

完全堆栈跟踪:

[ERROR] Java heap space -> [Help 1] 
java.lang.OutOfMemoryError: Java heap space 
    at java.util.IdentityHashMap.resize(IdentityHashMap.java:452) 
    at java.util.IdentityHashMap.put(IdentityHashMap.java:428) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:116) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.buildConflictGroups(JavaEffectiveScopeCalculator.java:129) 
    at org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.transformGraph(JavaEffectiveScopeCalculator.java:64) 
    at org.sonatype.aether.util.graph.transformer.ChainedDependencyGraphTransformer.transformGraph(ChainedDependencyGraphTransformer.java:75) 
    at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:253) 
    at org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:345) 
    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:131) 
    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:171) 
    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:108) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) 
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) 
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) 
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) 
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) 
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) 
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) 
+0

你能带-X运行呢?只是为了看看它失败的地方... – ivoruJavaBoy

+0

你可以试试更新版本的Maven吗?这看起来像一个错误。至少尝试'3.0.5'。已经有一个'3.2.1'。你使用的是什么版本的Java? – carlspring

+0

@carlspring我正在使用Java 1.6u51 x64。我要测试Maven的3.2.1 – Chris

回答

0

至少升级到Maven的3.0.5。这看起来像Maven中的一个错误。考虑升级到更高版本,例如3.2.1

相关问题