vavr-io / vavr-gwt Goto Github PK

View Code? Open in Web Editor NEW

22.0 9.0 4.0 71 KB

GWT module for Vavr

Java 100.00%

gwt vavr immutable-collections persistent-collections

vavr-gwt's Introduction

GWT support for Vavr

Using Vavr in GWT maven projects

Add the following maven dependency to your project:

<dependency>
    <groupId>io.vavr</groupId>
    <artifactId>vavr-gwt</artifactId>
    <version>{vavr-current-version}</version>
</dependency>

Inherit the Vavr module in your GWT module's descriptor file:

<module>
    <!-- ... -->
    <inherits name="Vavr"/>
    <!-- ... -->
</module>

Use the Vavr APIs in your code.

vavr-gwt's People

Contributors

Stargazers

Watchers

Forkers

ruslansennov nfekete mincong-h timmattison

vavr-gwt's Issues

Add a pre-build step in order to mark certain core Vavr methods as @GwtIncompatible

Hi,

with modularization, I want to get rid of the @GwtIncompatible annotations of the core Vavr lib.

Goal/Acceptance Criteria:

Let the GWT compiler know which methods are not compatible without using the @GwtIncompatible annotation(s) within the core Vavr library. For example this could be achieved by adding a pre-build step to the vavr-gwt Maven build.

See this Twitter conversation about how to use ByteBuddy to solve this issue.

In detail, I would suggest to explode the dependencies of vavr-gwt into the file system in a pre-build step. Furthermore we are able to rewrite/enhance the classes of our dependencies by dynamically annotating the according methods with vavr-gwt's own @GwtIncompatible annotation. After that, the GWT compiler is expected to work as desired.

I will add the list of methods later here.

Future is now based on Executor instead of ExecutorService

My latest changes on Vavr's Future broke the build.
I will try to fix that...

Any plans to update to the latest vavr version?

Are you accepting and merging PRs for it? It would be nice to use Vavr 0.10.3 in GWT.

Finish project setup

Connect to Travis-CI
Create a more mature README.md with badges etc.
Javaslang core build: Trigger javaslang-gwt when core build succeeded
split javaslang-gwt and javaslang-gwt-example into two repos
travis: after_success: mvn clean deploy -DskipTests --settings .travis/maven-settings.xml

Note: Moved the last steps to #4

GwtIIncompatible annotated io.vavr.collection.JavaConverters.ListView.toArray(U[]) breaks GWT compilation on depending modules

The error I get is the following:
The type JavaConverters.ListView<T,C> must implement the inherited abstract method Collection<T>.toArray(T[]).

I am not sure why this is happening as the method should be ignored by GWT compiler and not dropped completely.

Overwriting the class with an empty toArray implementation and removing the @GwtIncompatible annotation helps.

Class::isAssignableFrom native java method can't be implemented in GWT

See vavr-io/vavr#1389

Last steps making javaslang-gwt deployable

Hi Ruslan,

could you please create a ticket at sonatype (same as for javaslang-jackson)? See OSSRH Guide.

Then the last todo is to add your credentials to our .travis.yml (see Travis Encryption Keys):

$ travis encrypt --org -r javaslang/javaslang 'SONATYPE_USER=<secret>' --add
$ travis encrypt --org -r javaslang/javaslang 'SONATYPE_PASS=<secret>' --add

Alright?