[ANN] (Unofficial) Elemental2 2.24 release

[Peter Donald]

Elemental2 provides type checked access to browser APIs for Java
code. This is done by using closure extern files and generating
JsTypes, which are part of the new JsInterop specification that
is implemented in both GWT and J2CL.

https://github.com/google/elemental2

This is an unofficial release to Maven Central under a different groupId.
Please don't bug the original authors. Versions are released on demand.

API Changes relative to Elemental2 version 2.23

elemental2-core:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-core&old=2.23&new=2.24
  - 39 non breaking changes.
  - 19 potentially breaking changes.
  - 49 breaking changes.
elemental2-dom:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-dom&old=2.23&new=2.24
  - 85 non breaking changes.
  - 68 potentially breaking changes.
  - 165 breaking changes.
elemental2-indexeddb:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-indexeddb&old=2.23&new=2.24
  - 1 non breaking changes.
elemental2-svg:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-svg&old=2.23&new=2.24
  - 1 breaking changes.
elemental2-webassembly:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-webassembly&old=2.23&new=2.24
  - 1 potentially breaking changes.

The complete set of Elemental2 API differences is available at

  https://jsinterop.github.io/api-diff/?key=elemental2&old=2.23&new=2.24

The Maven dependencies can be added to your pom.xml via

    <dependency>
      <groupId>org.realityforge.com.google.elemental2</groupId>
      <artifactId>${artifact-id}</artifactId>
      <version>2.24</version>
    </dependency>

where artifact-id is one of

* elemental2-core
* elemental2-dom
* elemental2-promise
* elemental2-indexeddb
* elemental2-svg
* elemental2-webgl
* elemental2-media
* elemental2-webstorage
* elemental2-webassembly

Hope this helps,

Peter Donald

[John Huss]

Out of curiosity, how did you get this project to build successfully? 

When I try to build it I see this:

$ ./bazel_build_test.sh 

ERROR: /Users/john/repos/elemental2/third_party/BUILD:21:1: no such target '@com_google_javascript_closure_compiler//:externs': target 'externs' not declared in package '' defined by /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD and referenced by '//third_party:es6_collections'

[Peter Donald]

On Wed, Jun 12, 2019 at 7:31 AM John Huss <john...@gmail.com> wrote:

Out of curiosity, how did you get this project to build successfully? 

When I try to build it I see this:

$ ./bazel_build_test.sh 

ERROR: /Users/john/repos/elemental2/third_party/BUILD:21:1: no such target '@com_google_javascript_closure_compiler//:externs': target 'externs' not declared in package '' defined by /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD and referenced by '//third_party:es6_collections'

My guess is that you need to do something like this

bazel clean --expunge

 

This will remove all downloaded repositories (i.e. the closure-compiler source code as well as the other remote dependencies) and rebuild them. I believe after that it should build cleanly.

HTH

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a7ddd14d-d72d-4f45-ab43-cecb13c267a0%40googlegroups.com.

--

Cheers,

Peter Donald

[Peter Donald]

On Wed, Jun 12, 2019 at 8:29 AM Peter Donald <pe...@realityforge.org> wrote:

On Wed, Jun 12, 2019 at 7:31 AM John Huss <john...@gmail.com> wrote:

Out of curiosity, how did you get this project to build successfully? 

When I try to build it I see this:

$ ./bazel_build_test.sh 

ERROR: /Users/john/repos/elemental2/third_party/BUILD:21:1: no such target '@com_google_javascript_closure_compiler//:externs': target 'externs' not declared in package '' defined by /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD and referenced by '//third_party:es6_collections'

My guess is that you need to do something like this

bazel clean --expunge

 

This will remove all downloaded repositories (i.e. the closure-compiler source code as well as the other remote dependencies) and rebuild them. I believe after that it should build cleanly.

That said I just ran this and it seems to be running against the last binary release of closure compiler ... not the current git repository ... which will not produce the same jar as I generated as the closure externs are outdated. I will need to poke around to figure out how to work arouns this.

--

Cheers,

Peter Donald

[John Huss]

That worked, thanks!