Skip to content
Bazel rules for GWT
Starlark Java Other
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.bazelci
example/src/main/java/io/bazel/sample
gwt
.gitignore
AUTHORS
CODEOWNERS
CONTRIBUTING.md
CONTRIBUTORS
LICENSE.txt
README.md
WORKSPACE

README.md

Build status

GWT Rules for Bazel

Overview

These build rules are used for building GWT applications with Bazel. Applications are compiled as .war files containing compiled JavaScript and other resources. GWT applications can also be run in Development Mode via bazel run.

Setup

To be able to use the GWT rules, you must provide bindings for the GWT jars and everything it depends on. The easiest way to do so is to add the following to your WORKSPACE file, which will give you default versions for GWT and each dependency:

http_archive(
  name = "io_bazel_rules_gwt",
  url = "https://github.com/bazelbuild/rules_gwt/archive/0.1.2.tar.gz",
  sha256 = "070493202eebcf4a43c2a9acdf365d404b494950b0bce3f6ce144d8af784e868",
  strip_prefix = "rules_gwt-0.1.2",
)
load("@io_bazel_rules_gwt//gwt:gwt.bzl", "gwt_repositories")
gwt_repositories()

If you want to use a different version of GWT or any of its dependencies, you must provide your own bindings. Remove the gwt_repositories() line above and add a bind rule for each of the following in your WORKSPACE:

Basic Example

Suppose you have the following directory structure for a simple GWT application:

[workspace]/
    WORKSPACE
    src/main/java/
        app/
            BUILD
            MyApp.java
            MyApp.gwt.xml
        lib/
            BUILD
            MyLib.java
        public/
            index.html

Here, MyApp.java defines the entry point to a GWT application specified by MyApp.gwt.xml which depends on another Java library MyLib.java. index.html defines the HTML page that links in the GWT application. To build this app, your src/main/java/app/BUILD can look like this:

load("@io_bazel_rules_gwt//gwt:gwt.bzl", "gwt_application")

gwt_application(
  name = "MyApp",
  srcs = glob(["*.java"]),
  resources = glob(["*.gwt.xml"]),
  modules = ["app.MyApp"],
  pubs = glob(["public/*"]),
  deps = [
    "//src/main/java/lib",
  ],
)

Now, you can build the GWT application by running bazel build src/main/java/app:MyApp. This will run the GWT compiler and place all of its output as well as index.html into bazel-bin/src/main/java/app/MyApp.war. You can also run bazel run src/main/java/app:MyApp-dev to run GWT development mode for the application. Once development mode has started, you can see the app by opening http://127.0.0.1:8888/index.html in a browser. Note that development mode assumes that all of your .java files are located under java/ or src/main/java/ - see details on the java_roots flag below if this is not the case.

For a complete example, see the example/ directory in this repository.

gwt_application

gwt_application(name, srcs, resources, modules, pubs, deps, output_root, java_roots, compiler_flags, compiler_jvm_flags, dev_flags, dev_jvm_flags):

Implicit output targets

  • <name>.war: archive containing GWT compiler output and any files passed in via pubs.
  • <name>-dev: script that can be run via bazel run to launch the app in development mode.
Attributes
name Name, required

A unique name for this rule.

srcs List of labels, optional

List of .java source files that will be compiled and passed on the classpath to the GWT compiler.

resources List of labels, optional

List of resource files that will be passed on the classpath to the GWT compiler, e.g. .gwt.xml, .ui.xml, and .css files.

modules List of strings, required

List of fully-qualified names of modules that will be passed to the GWT compiler. Usually contains a single module name corresponding to the application's .gwt.xml file.

pubs List of labels, optional

Files that will be copied directly to the output war, such as static HTML or image resources. Not interpreted by the GWT compiler.

deps List of labels, optional

List of other java_libraries on which the application depends. Both the class jars and the source jars corresponding to each library as well as their transitive dependencies will be passed to the GWT compiler's classpath. These libraries may contain other .gwt.xml, .ui.xml, etc. files as resources.

output_root String, optional

Directory in the output war in which all outputs will be placed. By default outputs are placed at the root of the war file.

java_roots List of strings, optional

Directories relative to the workspace root that form roots of the Java package hierarchy (e.g. they contain com directories). By default this includes java, javatests, src/main/java and src/test/java. If your Java files aren't under these directories, you must set this property in order for development mode to work correctly. Otherwise GWT won't be able to see your source files, so you will not see any changes reflected when refreshing dev mode.

compiler_flags List of strings, optional

Additional flags that will be passed to the GWT compiler. See here for a list of available flags.

compiler_jvm_flags List of strings, optional

Additional JVM flags that will be passed to the GWT compiler, such as -Xmx4G to increase the amount of available memory.

dev_flags List of strings, optional

Additional flags that will be passed to development mode. See here for a list of available flags.

dev_jvm_flags List of strings, optional

Additional JVM flags that will be passed to development mode, such as -Xmx4G to increase the amount of available memory.

You can’t perform that action at this time.