https://kotlinlang.org logo
Channels
Powered by
#spring
  • s

    sdeleuze

    09/28/2017, 7:59 PM
    But Boot 2 is not GA yet
  • s

    sdeleuze

    09/28/2017, 7:59 PM
    Will be in late december
  • s

    sdeleuze

    09/28/2017, 7:59 PM
    That said it is pretty stable
  • s

    sdeleuze

    09/28/2017, 8:00 PM
    MiXiT runs in production for months without any single crash
    👏 2
  • m

    m

    09/28/2017, 8:00 PM
    great to know.
  • m

    m

    09/28/2017, 8:01 PM
    @sdeleuze I got the same error with latest master and command line.
  • m

    m

    09/28/2017, 8:01 PM
    this happens with other projects too.
  • m

    m

    09/28/2017, 8:02 PM
    strange.
  • m

    m

    09/28/2017, 8:05 PM
    Copy code
    Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'mappingMongoConverter' defined in class path resource [org/springframework/boot/autoconfigure/data/mongo/MongoDataAutoConfiguration.class]: Unsatisfied dependency expressed through method 'mappingMongoConverter' parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mongoMappingContext' defined in class path resource [org/springframework/boot/autoconfigure/data/mongo/MongoDataAutoConfiguration.class]: Invocation of init method failed; nested exception is java.lang.VerifyError: Uninitialized object exists on backward branch 119
Exception Details:
  Location:
    mixit/model/Post.<init>(Ljava/lang/String;Ljava/time/LocalDateTime;Ljava/util/Map;Ljava/util/Map;Ljava/util/Map;Ljava/lang/String;Ljava/util/Map;ILkotlin/jvm/internal/DefaultConstructorMarker;)V @207: goto
  Reason:
    Error exists in the bytecode
  • s

    sdeleuze

    09/28/2017, 8:06 PM
    Hum super strange
  • s

    sdeleuze

    09/28/2017, 8:07 PM
    Can somebody else reproduce ?
  • m

    m

    09/28/2017, 8:07 PM
    it looks like a low level problem.
  • s

    sdeleuze

    09/28/2017, 8:08 PM
    Yeah
  • m

    m

    09/28/2017, 8:08 PM
    but kotlin gets downloaded freshly.
  • m

    m

    09/28/2017, 8:08 PM
    some bug with my java version? unlikely.
  • s

    sdeleuze

    09/28/2017, 8:08 PM
    Are you using 
    ./gradlew
    and not 
    gradle
    ?
  • m

    m

    09/28/2017, 8:08 PM
    yes gradelw.
  • s

    sdeleuze

    09/28/2017, 8:10 PM
    Could you delete your Gradle cache in 
    ~/.gradle/cache/
    ?
    👍 1
  • s

    sdeleuze

    09/28/2017, 8:10 PM
    And rerun the build
  • n

    nfrankel

    09/28/2017, 8:10 PM
    or just use a proper build tool? 🧌
    😛 1
  • s

    sdeleuze

    09/28/2017, 8:13 PM
    I cleaned my cache 
    ./gradlew clean test
    is fine
  • s

    sdeleuze

    09/28/2017, 8:14 PM
    And on your side ?
  • m

    m

    09/28/2017, 8:43 PM
    @sdeleuze nope the same error 😞
  • s

    sdeleuze

    09/28/2017, 8:49 PM
    Sorry I don't understand
  • s

    sdeleuze

    09/28/2017, 8:49 PM
    If somebody else can reproduce I can have a deeper look
  • s

    sdeleuze

    09/28/2017, 8:49 PM
    If not, I don't think I can do much more
  • s

    sdeleuze

    09/28/2017, 9:13 PM
    @m Eventually create a Kotlin issue with maximum of infos on you environement (OS, java version, etc.) and the detailed error message.
  • m

    m

    09/28/2017, 9:14 PM
    it looks like it's specific to me.
  • s

    sdeleuze

    09/28/2017, 9:14 PM
    Usually this kind of low level error come from Gradle old files
  • m

    m

    09/28/2017, 9:14 PM
    when I google the error 
    "java.lang.VerifyError: Uninitialized object exists on backward branch"
    I mostly get scala/sbt bugs
1...119120121...173Latest