Can't Build Geronimo server trunk after upgrading to ASM 4.0
------------------------------------------------------------

                 Key: GERONIMO-6301
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6301
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: buildsystem, core
    Affects Versions: 3.0
         Environment: Any build environment.
My build environment: CentOS 6.2-64bit, OpenJDK 1.6-64bit, Maven 3.0.4
            Reporter: Ulrich Romahn
            Priority: Blocker


Some component (most likely Apache Karaf 3.0-SNAPSHOT) upgraded the ASM library 
from 3.x to 4.0. This upgrade breaks the build.

The build "hangs" at the following step: Building Geronimo Plugins, System 
Database :: System Database 3.0-SNAPSHOT

Which is producing the following exception:
[INFO]   
org.apache.geronimo.configs/j2ee-deployer/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-deployer/3.0-SNAPSHOT/car,j2eeType=ModuleBuilder,name=GBeanRefBuilder
 
[INFO] Exception, use console to investigate 
java.lang.reflect.InvocationTargetException 
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
        at java.lang.reflect.Method.invoke(Method.java:616) 
        at 
org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:456)
 
        at 
org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:311)
 
        at 
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:214) 
        at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
 
        at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) 
        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:320) 
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) 
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) 
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) 
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
        at java.lang.reflect.Method.invoke(Method.java:616) 
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
 
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) 
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
 
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) 
Caused by: java.lang.NoClassDefFoundError: 
org/objectweb/asm/commons/EmptyVisitor 
        at java.lang.ClassLoader.defineClass1(Native Method) 
        at java.lang.ClassLoader.defineClass(ClassLoader.java:634) 
        at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2128)
 
        at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1432)
 
        at 
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
 
        at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
 
        at java.lang.ClassLoader.loadClass(ClassLoader.java:266) 
        at 
org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.initContext(ConnectorModuleBuilder.java:437)
 
        at 
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:688)
 
        at 
org.apache.geronimo.deployment.DeployerImpl.deploy(DeployerImpl.java:322) 
        at 
org.apache.geronimo.deployment.DeployerImpl.deploy(DeployerImpl.java:204) 
        at 
org.apache.geronimo.deployment.DeployerImpl.deploy(DeployerImpl.java:172) 
        ... 28 more 
Caused by: java.lang.ClassNotFoundException: 
org.objectweb.asm.commons.EmptyVisitor not found by org.objectweb.asm.all [12] 
        at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
 
        at 
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
 
        at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
 
        at java.lang.ClassLoader.loadClass(ClassLoader.java:266) 
        at 
org.apache.felix.framework.BundleWiringImpl.getClassByDelegation(BundleWiringImpl.java:1317)
 
        at 
org.apache.felix.framework.BundleWiringImpl.searchImports(BundleWiringImpl.java:1481)
 
        at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1427)
 
        at 
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
 
        at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
 
        at java.lang.ClassLoader.loadClass(ClassLoader.java:266) 
        ... 40 more 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to