Benjamin Reed created KARAF-5878:
------------------------------------

             Summary: karaf-maven-plugin fails on large project
                 Key: KARAF-5878
                 URL: https://issues.apache.org/jira/browse/KARAF-5878
             Project: Karaf
          Issue Type: Bug
    Affects Versions: 4.2.1
            Reporter: Benjamin Reed


I'm having a hard time narrowing down where things have gone wrong but we've 
started seeing this exception repeatably in our build:

 

 
{code:java}
[ERROR] Failed to execute goal 
org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:assembly (default-assembly) 
on project org.opennms.container.shared: Unable to build assembly: -1 -> [Help 
1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
goal org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:assembly 
(default-assembly) on project org.opennms.container.shared: Unable to build 
assembly at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146) at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject[DEBUG] 
Connection manager is shutting down (LifecycleModuleBuilder.java:117) at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81) at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:51) at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute[DEBUG] Connection 
manager shut down (LifecycleStarter.java:128) at 
org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) at 
org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) at 
org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) at 
org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) at 
org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) at 
org.apache.maven.cli.MavenCli.main (MavenCli.java:194) at 
sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke 
(Method.java:498) at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229) at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: 
Unable to build assembly at org.apache.karaf.tooling.AssemblyMojo.execute 
(AssemblyMojo.java:448) at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:134) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146) at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117) at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81) at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:51) at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute 
(DefaultMaven.java:309) at org.apache.maven.DefaultMaven.doExecute 
(DefaultMaven.java:194) at org.apache.maven.DefaultMaven.execute 
(DefaultMaven.java:107) at org.apache.maven.cli.MavenCli.execute 
(MavenCli.java:955) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) 
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) at 
sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke 
(Method.java:498) at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229) at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at 
java.util.ArrayList.elementData (ArrayList.java:422) at java.util.ArrayList.set 
(ArrayList.java:450) at org.apache.felix.resolver.util.ShadowList.replace 
(ShadowList.java:74) at org.apache.felix.resolver.Candidates.prepare 
(Candidates.java:941) at 
org.apache.felix.resolver.ResolverImpl.getInitialCandidates 
(ResolverImpl.java:505) at org.apache.felix.resolver.ResolverImpl.doResolve 
(ResolverImpl.java:390) at org.apache.felix.resolver.ResolverImpl.resolve 
(ResolverImpl.java:378) at org.apache.felix.resolver.ResolverImpl.resolve 
(ResolverImpl.java:350) at 
org.apache.karaf.features.internal.region.SubsystemResolver.resolve 
(SubsystemResolver.java:257) at 
org.apache.karaf.features.internal.service.Deployer.deploy (Deployer.java:388) 
at org.apache.karaf.features.internal.service.Deployer.deployFully 
(Deployer.java:330) at org.apache.karaf.profile.assembly.Builder.resolve 
(Builder.java:1993) at org.apache.karaf.profile.assembly.Builder.startupStage 
(Builder.java:1804) at 
org.apache.karaf.profile.assembly.Builder.doGenerateAssembly 
(Builder.java:1097) at 
org.apache.karaf.profile.assembly.Builder.generateAssembly (Builder.java:847)
at org.apache.karaf.tooling.AssemblyMojo.doExecute (AssemblyMojo.java:542) at 
org.apache.karaf.tooling.AssemblyMojo.execute (AssemblyMojo.java:444) at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:134) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154) at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146) at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117) at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81) at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:51) at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute 
(DefaultMaven.java:309) at org.apache.maven.DefaultMaven.doExecute 
(DefaultMaven.java:194) at org.apache.maven.DefaultMaven.execute 
(DefaultMaven.java:107) at org.apache.maven.cli.MavenCli.execute 
(MavenCli.java:955) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) 
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) at 
sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke 
(Method.java:498) at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229) at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356) [ERROR] [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/MojoExecutionException [ERROR] 
child exited with value 1
{code}
 

I've attempted a git bisect but the results are inconclusive, because sometimes 
things that previously passed now fail, even if I clear out ~/.m2/repository 
and wipe all the target directories.  This makes me wonder if our project has 
just gotten big enough that we're hitting some kind of limit.

 Any ideas what could be causing this?

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to