Skip to content

Releases: blutorange/closure-compiler-maven-plugin

v2.11.0

21 Oct 21:16
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler version v20190909

v2.10.0

31 Aug 16:08
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler version v20190819

v2.9.0

09 Aug 17:54
Compare
Choose a tag to compare
  • Update to closure compiler version v20190729
  • Add a new option skipMode with the options NEWER (default) and EXISTS. Even outside of Eclipse incremental builds, this plugin
    now skips an execution if the output files exist (skipMode=EXISTS) and are younger than the input files (skipMode=NEWER). In case you
    do not want to skip an execution no matter what, set the option force to true. See also #51

v2.8.0

23 Jul 20:05
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler version v20190709
  • Fix #50

v2.7.0

26 Jun 04:43
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler version v20190618
  • Add option skip, see ticket #49

v2.6.0

20 Jun 18:18
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler version v20190528.
  • Update some maven dependencies.
  • Add a few more examples / tests.

v2.5.0

11 May 16:51
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Add new option closureJsModuleRoot (see #48).
  • When passing source files to closure compiler, their file names are now relative to the specified source directory (srcDir). When the source
    directory is set to the npm directory with the node_modules folder, closure compiler is now able to resolve installed node modules.
  • Add a new option closureSourceMapLocationMappings. When not set, the references to the source files in the source map are relative
    to their locations on the file system (as in previous versions)
  • Update to closure compiler v20190415

v2.4.0

13 Apr 05:50
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler v20190325
  • Ticket #47: Preserve relative file names when not merging the files
  • The option outputFileName now allows for the additional variable #{path}: When not
    merging the input files, this is the relative path from the source directory to the source
    file. The default for this options is now #{path}/#{basename}.min.#{extension}
    For example: Assume the source dir is /my/dir and the target dir is /my/target. Also assume
    that you want to minify the two files /my/dir/a/file1.js and /my/dir/b/file2.js, without merging them.
    Then by default, the minified files are written to /my/target/a/file1.min.js and /my/target/b/file1.min.js.
    Previously, they would have been written to /my/target/file1.min.js and /my/target/file2.min.js.

v2.3.0

22 Mar 19:24
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler v20190301
  • Default language for closureLanguageIn is now ECMASCRIPT_2018
  • Add test for closureSourceMapOutputType

v2.2.0

03 Mar 07:26
Compare
Choose a tag to compare

See also the closure compiler changelog.

  • Update to closure compiler v20190215
  • Fix issue #46 for good