2014-04-15 40 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

相關問題