search

cincheo / jsweet

A Java to JavaScript transpiler.
http://www.jsweet.org
Other
1.46k stars 161 forks source link

No Javascript output #728

Closed vorth closed 2 years ago

vorth commented 2 years ago

Since upgrading to 3.0, I no longer see any Javascript generated. I have been "living with" 108 errors from the TS-to-JS phase using 2.4, since most or all are not on code paths I need, and the Javascript was generated in any case.

Is it now necessary to specifically instruct the TS compiler to generate Javascript in spite of errors?

My settings:

extraSystemPath: null encoding: UTF-8 classpath: ... ts output dir: null js output dir: online/jsweetOut/js ts only: false declarations: null declarationOutDir: null candiesJsOutDir: null bundle: true ecmaTargetVersion: ES6 moduleKind: none sourceMaps: false SourceRoot: null jdkHome: /Library/Java/JavaVirtualMachines/jdk-17.0.4.jdk/Contents/Home definitions: true disableSinglePrecisionFloats: false factoryClassName: null ignoreJavaFileNameError: null tscWatchMode: null javaCompilerExtraOptions: -source,1.8,-target,1.8 source includes: ... source excludes: ... sources dirs: ... sourceFiles: ...

vorth commented 2 years ago

Found the problem... in 2.4, a path like "x/y/z" was interpreted relative to the Gradle root project directory. Now it is interpreted relative to the process, so it ends up inside the Gradle worker area. Using absolute paths resolved my problem.