Re: [ANNOUNCE] (Unofficial) Elemental2 1.0.0-b14-2f97dbe packages published to Maven Central

Thank you! I wish the core elemental team was doing those releases  ...

On Sunday, February 3, 2019 at 5:57:12 PM UTC-8, Peter Donald wrote:

Version 1.0.0-b15-7a28038 has been published to Maven Central (but it may take an hour or so to be replicated out). A problem was identified - namely ClientRect disappeared from the API due to a change in closure ~12 days ago. See https://github.com/google/elemental2/pull/80 for the fix.

It was suggested that one way to help identify changes and problems ahead of time is to generate one of the API diffs via something like japicmp (See http://siom79.github.io/japicmp/Examples.html for some examples). I was thinking about producing this against the baseline build (i.e. last official elemental2 publish) and the previous build. 

Before I did this - would anyone find this useful? And/or has anyone got any better ideas on how to trace API evolution over time?

On Sun, Feb 3, 2019 at 11:47 PM Peter Donald <pe...@realityforge.org> wrote:

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 both implemented in GWT and J2CL.

The official Elemental2 project is available via

https://github.com/google/elemental2

The Elemental2 project does not yet provide regular releases but

is evolving as the underlying Closure compiler externs evolve and

this can make it difficult to adopt Elemental2 in more traditional

build systems.

Until regular Elemental2 releases start occurring, I have decided

to periodically publish versions of Elemental2 artifacts to maven

central. To avoid conflicts with the official releases the groupId

of the artifacts are prefixed with "org.realityforge." and artifacts

use different versions.

This is completely unofficial so please don't bug the original

Elemental2 authors. A new version will be released when I need a

feature present in newer externs or when I am explicitly asked.

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

    <dependency>

      <groupId>org.realityforge.com.google.elemental2</groupId>

      <artifactId>${artifact-id}</artifactId>

      <version>1.0.0-b14-2f97dbe</version>

    </dependency>

where artifact-id is one of

* elemental2-core

* elemental2-dom

* elemental2-promise

* elemental2-indexeddb

* elemental2-svg

* elemental2-webgl

* elemental2-media

* elemental2-webstorage

To see how these artifacts are published see:

https://github.com/realityforge/repackr

Hope it helps someone,

Peter Donald

--

Cheers,

Peter Donald

--
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-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.