Skip to content

com.sun.tools.javac.jvm.ClassReader$BadClassFile: bad class file when using j4ts #42

@tinca

Description

@tinca

Hi,

I try to get an answer to this issue:
cincheo/jsweet#491

My gradle build file contains:

buildscript {
...
    dependencies {
        classpath('org.jsweet:jsweet-gradle-plugin:2.2.0-SNAPSHOT') { //
            transitive = true }
    }
}
...
dependencies {
    compile group: 'org.jsweet', name: 'jsweet-core', version:'6-SNAPSHOT'
    compile group: 'org.jsweet', name: 'jsweet-transpiler', version:'2.2.0-SNAPSHOT'
    compile group: 'org.jsweet.candies.ext', name: 'angular', version:'1.4.0-SNAPSHOT'
    compile group: 'org.jsweet.candies.ext', name: 'angular-route', version:'1.2.0-SNAPSHOT'
    compile group: 'org.jsweet.candies.trusted', name: 'es6-promise', version:'0.0.0-SNAPSHOT'
    compile 'org.jheaps:jheaps:0.9'
    compile group: 'org.jsweet', name: 'j4ts', version:'0.5.0'
}

However j4ts pom.xml defines jsweet 2.0.0. I tried to change that to 2.2.0 in a fork, but that gives a lot of errors.
I tried to change jsweet (and plugin) to 2.0.0 to no avail.
It seems j4ts is not in sync with current jsweet.

I am keen in testing jsweet on a real project e.g. transpiling JGraphT and if that is successful my project that builds on that, too.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions