jsweet-maven-plugin
jsweet-maven-plugin copied to clipboard
JSweet maven plugin providing build and clean operations of JSweet sources
With the change in jsweet "Use system-wide temporary working directories, clean up after use", this brittle code is no longer required.
Align with the change in jsweet "Allow testing from parent pom; remove test path from transpiler"
Move signing to a profile called "signed"; invoke with mvn clean install -Dsigned
`Added a config param to allow non-compile scoped dependencies on the classpath for the jsweet mojos` My use-case is that I have a standalone library that is built and deployed...
Bumps [org.apache.maven:maven-core](https://github.com/apache/maven) from 3.6.3 to 3.8.1. Commits 05c21c6 [maven-release-plugin] prepare release maven-3.8.1 d295dc3 [MNG-7128] keep blocked attribute from mirrors in artifact repositories a469068 next version in branch 3.8.x is 3.8.1-SNAPSHOT...
Bumps [org.apache.maven:maven-compat](https://github.com/apache/maven) from 3.6.3 to 3.8.1. Commits 05c21c6 [maven-release-plugin] prepare release maven-3.8.1 d295dc3 [MNG-7128] keep blocked attribute from mirrors in artifact repositories a469068 next version in branch 3.8.x is 3.8.1-SNAPSHOT...
* name: candy=true or candyBuild=true or candyMode=true * automatically set the generated js and d.ts files in the META-INF directory (in order to simplify candy creation) * generate the candy-metadata.json...
JSweet v2 should support passing parameters to the transpiler defined within ``jsweetconfig.json``. These parameters will be overridden by local parameters, such as command-line parameters and Maven ``pom.xml`` parameters. The problem...
The bundle produced with `true` won't work in the browser because none of the candy dependencies are included. I'm not sure I didn't miss something here, but I found an...