Grails

Repeated Spring Annotation exception causes application crash on RunApp

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 2.0-RC1
  • Fix Version/s: 2.0-RC2
  • Component/s: ContinuousBuild
  • Labels:
    None
  • Testcase included:
    yes

Description

 Running Grails application
| Error 2011-10-28 18:14:22,274 [Thread-8] ERROR context.GrailsContextLoader  - Error executing bootstraps: Error creating bean with name 'grailsApplicationPostProcessor': Initialization of bean failed; nested exception is java.lang.NoSuchMethodError: org.springframework.core.annotation.AnnotationUtils.getAnnotation(Ljava/lang/reflect/AnnotatedElement;Ljava/lang/Class;)Ljava/lang/annotation/Annotation;
Message: Error creating bean with name 'grailsApplicationPostProcessor': Initialization of bean failed; nested exception is java.lang.NoSuchMethodError: org.springframework.core.annotation.AnnotationUtils.getAnnotation(Ljava/lang/reflect/AnnotatedElement;Ljava/lang/Class;)Ljava/lang/annotation/Annotation;
   Line | Method
->> 303 | innerRun in java.util.concurrent.FutureTask$Sync
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
|   138 | run      in java.util.concurrent.FutureTask
|   886 | runTask  in java.util.concurrent.ThreadPoolExecutor$Worker
|   908 | run      in     ''
^   662 | run . .  in java.lang.Thread

To replicate, run app in instance of Grails 2.0.0RC1. Works fine first time. Stop server, try to run again.

Have to resolve by blamming away grails cache. Probably caused by a plugin dependency, likely candidate CXF. These seem like the "gotcha bugs" that upgrades should be on the lookout for though.

  1. File
    CommandObjectTest.7z
    28/Oct/11 6:20 PM
    143 kB
    Nicholas Vaidyanathan

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graeme Rocher added a comment -

Almost certainly a spring conflict, will investigate

Show
Graeme Rocher added a comment - Almost certainly a spring conflict, will investigate
Hide
Permalink
Graeme Rocher added a comment -

The issue here is Apache CXF requiring Spring 3.0.4 and the fact that you have defined the plugin has a build time dependency.

You have 2 options. Either define the plugin as a compile time dependency:

        compile( ":cxf:0.7.0" )

That way conflict resolution kicks in and Spring 3.1 is chosen automatically or you need to configure your excludes appropriately:

    dependencies {
        // specify dependencies here under either 'build', 'compile', 'runtime', 'test' or 'provided' scopes eg.

        // runtime 'mysql:mysql-connector-java:5.1.16'
        build( "org.apache.cxf:cxf-rt-frontend-jaxrs:2.3.0" ) {
            excludes "cxf-rt-transports-http", "spring-core"
        }
        build( "org.apache.cxf:cxf-rt-transports-http:2.3.0" ) {
            excludes "spring-web"
        }        
    }

    plugins {
        ...
        build( ":cxf:0.7.0" ) {
            excludes "cxf-rt-frontend-jaxrs"
        }
    }
Show
Graeme Rocher added a comment - The issue here is Apache CXF requiring Spring 3.0.4 and the fact that you have defined the plugin has a build time dependency. You have 2 options. Either define the plugin as a compile time dependency: compile( ":cxf:0.7.0" ) That way conflict resolution kicks in and Spring 3.1 is chosen automatically or you need to configure your excludes appropriately: dependencies { // specify dependencies here under either 'build', 'compile', 'runtime', 'test' or 'provided' scopes eg. // runtime 'mysql:mysql-connector-java:5.1.16' build( "org.apache.cxf:cxf-rt-frontend-jaxrs:2.3.0" ) { excludes "cxf-rt-transports-http" , "spring-core" } build( "org.apache.cxf:cxf-rt-transports-http:2.3.0" ) { excludes "spring-web" } } plugins { ... build( ":cxf:0.7.0" ) { excludes "cxf-rt-frontend-jaxrs" } }
Hide
Permalink
Nicholas Vaidyanathan added a comment -

Cool. Stupid question: is there a general heuristic for when plugins should be included as "build" versus "compile"? Since I don't see anything specific in http://grails.org/doc/latest/guide/3.%20Configuration.html#3.7%20Dependency%20Resolution, I've just tried to follow patterns from defaults (e.g. "hibernate looks like it's included at build. I should do that too")

Show
Nicholas Vaidyanathan added a comment - Cool. Stupid question: is there a general heuristic for when plugins should be included as "build" versus "compile"? Since I don't see anything specific in http://grails.org/doc/latest/guide/3.%20Configuration.html#3.7%20Dependency%20Resolution , I've just tried to follow patterns from defaults (e.g. "hibernate looks like it's included at build. I should do that too")

People

  • Assignee:
    Unassigned
    Reporter:
    Nicholas Vaidyanathan
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: