This plugin is a rewrite of code present in
https://github.com/Vertispan/j2clmavenplugin
For a full list of contributors, read source and to more click here
A major difference between the two is this plugin requires most parameters and dependencies to be declared as Maven artifacts, nothing is assumed, everything must be declared in the pom in some form. As much as possible nothing is defaulted and must be present in the POM.
The preferred way to use the plugin is to checkout the source
git clone git://github.com/mP1/j2cl-maven-plugin.git
and build and install with Maven.
mvn clean install
Note this plugin has issues working with Maven 3.8.3, the recommended version to use is Maven 3.6.3.
The plugin supports the following goals
-
build
: executes a single compilation, typically to produce a JS application or library. -
clean
: cleans up all the cache directory. -
test
: executes junit 3 tests. -
watch
: builds the project and then watches for file changes and rebuilds
Sample required plugin repositories
<pluginRepositories>
<pluginRepository>
<id>github-mp1-appengine-repo</id>
<url>https://maven-repo-254709.appspot.com</url>
</pluginRepository>
<pluginRepository>
<id>google-snapshots</id>
<name>google-snapshots</name>
<url>https://oss.sonatype.org/content/repositories/google-snapshots/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>vertispan-releases</id>
<name>Vertispan hosted artifacts-releases</name>
<url>https://repo.vertispan.com/j2cl</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>vertispan-snapshots</id>
<name>Vertispan Snapshots</name>
<url>https://repo.vertispan.com/gwt-snapshot/</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>sonatype-snapshots-repo</id>
<url>https://oss.sonatype.org/content/repositories/snapshots</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>sonatype-repo</id>
<url>https://oss.sonatype.org/content/repositories/repositories</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
</pluginRepository>
</pluginRepositories>
A sample plugin declaration follows which mentions all parameters. The numerous parameters are used by the plugin during the orchestration and processing of the source and other files to eventually produce the output directory which will be filled with the equivalent javascript.
<plugin>
<groupId>walkingkooka</groupId>
<artifactId>j2cl-maven-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<executions>
<execution>
<id>build-js</id>
<phase>prepare-package</phase>
<goals>
<goal>build</goal>
</goals>
<configuration>
<classpath-scope>runtime</classpath-scope>
<!--
BUNDLE, WHITESPACE_ONLY, SIMPLE, ADVANCED
-->
<compilation-level>ADVANCED</compilation-level>
<defines>
<jre.checkedMode>DISABLED</jre.checkedMode>
<jre.checks.checkLevel>MINIMAL</jre.checks.checkLevel>
<jsinterop.checks>DISABLED</jsinterop.checks>
</defines>
<entry-points>example.helloworld.app</entry-points>
<externs></externs>
<formatting>
<!--
PRETTY_PRINT | PRINT_INPUT_DELIMITER | SINGLE_QUOTES
-->
<param>PRETTY_PRINT</param>
<param>PRINT_INPUT_DELIMITER</param>
<param>SINGLE_QUOTES</param>
</formatting>
<!--
ECMASCRIPT3,
ECMASCRIPT5,
ECMASCRIPT5_STRICT,
ECMASCRIPT_2015,
ECMASCRIPT_2016,
ECMASCRIPT_2017,
ECMASCRIPT_2018,
ECMASCRIPT_2019,
STABLE
-->
<language-out>ECMASCRIPT_2016</language-out>
<!-- when true a sources sub-directory will appear below the main javascript -->
<sourceMaps>sources/</sourceMaps>
<thread-pool-size>0</thread-pool-size>
<classpath-required>
<param>group-id-1:artifact-id-2:*</param>
<param>group-id-1:artifact-id-2:version-3</param>
</classpath-required>
<ignored-dependencies/>
<javascript-source-required/>
</configuration>
</execution>
</executions>
</plugin>
This option is only available within the test
task, and controls the log level of test messages that will appear in
the browser console.
(classpathscope=test
).
- NONE
- DEBUG
- INFO
- WARN
- ERROR
- ALL
<browser-log-level>ALL</browser-log-level>
The sample log below includes some logging both of the report and other logging messages printed during test execution.
INFO: Detected dialect: W3C
[INFO] CHROME
[INFO] Test Report
[INFO] j2cl-maven-plugin test runner [PASSED]
[INFO] /Users/miroslav/repos-github/j2cl-maven-plugin/target/it-tests/junit-test-browser-log-level/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test-browser-log-level--jar--1.0-810114ee72641960e5b4c1b3aa2841a9797586f3/8-closure-compile/output/test.JunitTest.html
[INFO] 4 of 4 tests run in 3.7200000369921327ms.
[INFO] 4 passed, 0 failed.
[INFO] 1 ms/test. 1 files loaded.
[INFO]
[INFO] Browser log
[INFO] SEVERE file:///Users/miroslav/repos-github/j2cl-maven-plugin/target/it-tests/junit-test-browser-log-level/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test-browser-log-level--jar--1.0-810114ee72641960e5b4c1b3aa2841a9797586f3/8-closure-compile/output/test.JunitTest.js 76:341 "Error message 4!!"
[INFO] WARNING file:///Users/miroslav/repos-github/j2cl-maven-plugin/target/it-tests/junit-test-browser-log-level/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test-browser-log-level--jar--1.0-810114ee72641960e5b4c1b3aa2841a9797586f3/8-closure-compile/output/test.JunitTest.js 76:448 "Warn message 3!!"
[INFO] All test(s) successful!
[INFO]
[INFO] Log file
[INFO] /Users/miroslav/repos-github/j2cl-maven-plugin/target/it-tests/junit-test-browser-log-level/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test-browser-log-level--jar--1.0-810114ee72641960e5b4c1b3aa2841a9797586f3/9-junit-tests/log.txt
[INFO]
A list of browsers that are used by webdriver to execute transpiled unit tests,(classpathscope=test
). At least
one must be selected out of the supported browsers listed below.
<browsers>
<param>CHROME</param>
<param>FIREFOX</param>
<param>HTML_UNIT</param>
</browsers>
If HTML_UNIT is selected the language-out
should be set to ECMASCRIPT5
as newer javascript constructs such as class
are not supported by the html unit javascript engine.
A list of artifacts that will be added to all classpaths. The first entry will be used as the bootstrap archive. If a
dependency is present here but absent in javascript-source-required
then it will never appear when js files are
required.
The snippet below is a good starting point and forcibly includes a few required artifacts.
<classpath-required>
<param>group1:artifact2:*</param>
<param>group1:artifact2:version3</param>
</classpath-required>
- Maven coordinates may have a wildcard in the version.
Archives with the following conditions will be automatically marked as equivalent to adding a classpath-required
entry.
- Annotation processors.
- JRE classes (including bootstrap).
- Only annotation class files.
- If the file
.walkingkooka-j2cl-maven-plugin-classpath-required.txt
is present.
The suggested value is typically compile
, for more info click here
<classpath-scope>compile</classpath-scope>
A closure compiler parameter that controls the closure task, for more info click here. The Closure Compiler lets you choose from three levels of compilation, ranging from simple removal of whitespace and comments to aggressive code transformations.
<compilation-level>ADVANCED</compilation-level>
These key value pairs are arguments given only to the Closure compiler. The fragment below is the recommended.
<defines>
<jre.checkedMode>DISABLED</jre.checkedMode>
<jre.checks.checkLevel>MINIMAL</jre.checks.checkLevel>
<jsinterop.checks>DISABLED</jsinterop.checks>
</defines>
A Closure compiler argument containing one or more entry point(s) (classpathscope=compile
).
<entrypoint>helloworld.app</entrypoint>
Key value pairs that define externs for the Closure compiler. For more info click here.
Zero or many formatting options that may be used to aide troubleshooting, or simply to produce pretty printed output. The sample below shows all available formatting options, some or all may be removed as necessary.
For more info click here
<formatting>
<param>PRETTY_PRINT</param>
<param>PRINT_INPUT_DELIMITER</param>
<param>SINGLE_QUOTES</param>
</formatting>
A list of artifacts that will not be processed. This is used to avoid processing any bootstrap and jre artifacts, as they come pre-processed, or only contain annotations that are not required during transpiling (j2cl) but necessary for compiling (javac).
<ignored-dependencies>
<param>group1:artifact2:*</param>
<param>group1:artifact2:version3</param>
</ignored-dependencies>
- Maven coordinates may have a wildcard in the version.
- Archives with the following conditions will automatically marked as equivalent to adding an
ignored-dependencies
entry.- Annotation processors.
- Dependency where classifier=sources pairs another dependency.
- JRE classes & javascript (including bootstrap).
- Only annotation class files.
[see](#Ignored dependencies)
The path to the initial script filename.
A list of artifacts that will be added to when javascript sources are being processed. If a dependency is present here
but absent in classpath-required
then it will never appear on a classpath.
The bootstrap and jre artifacts mentioned below are the transpiled versions of similar artifacts that appear in <classpath-required
,
and the later includes numerous classes and mostly annotations that provide hints to the transpilation process.
The snippet below is a good starting point and forcibly includes a few minimally required artifacts.
<javascript-source-required>
<param>group1:artifact2:*</param>
<param>group1:artifact2:version3</param>
</javascript-source-required>
- Maven coordinates may have a wildcard in the version.
- Archives with the following conditions will automatically marked as equivalent to adding
a
javascript-source-required
entry.- Archives with only JRE javascript (including bootstrap).
[see](#Javascript source required file(s))
This may be used to pass additional arguments to javac such as an annotation processor argument.
<java-compiler-arguments>
<param>-Aannotation-processor-argument=value</param>
</java-compiler-arguments>
The output language (javascript variant) of the resulting javascript.
For a detailed list of available language out options click here.
The xml snippet below includes all currently available options, only one may be set, more than one is an error.
<language-out>ECMASCRIPT3</language-out>
<language-out>ECMASCRIPT5</language-out>
<language-out>ECMASCRIPT5_STRICT</language-out>
<language-out>ECMASCRIPT_2015</language-out>
<language-out>ECMASCRIPT_2016</language-out>
<language-out>ECMASCRIPT_2017</language-out>
<language-out>ECMASCRIPT_2018</language-out>
<language-out>ECMASCRIPT_2019</language-out>
This path is the final location of the final javascript (classpathscope=compile
).
Accepts a relative path to the target of directory of initial-script-filename
where source files will be copied. This
will typically be a sub-directory perhaps called sources
under the same directory receiving the main javascript output
file. Click here for more details
about .map
files and how source maps work.
<source-maps>sources/</source-maps>
This is only available when executing tests, and provides an easy switch to turn tests on/off (skip=true
).
<skip>false</skip>
From the command line the property may be set -Dwalkingkooka.j2cl.maven.plugin.test.skip=true
.
A block of multiple test
entries each defining a GLOB pattern to match test suites class names (classpathscope=test
).
<tests>
<test>org.gwtproject.timer.client.TimerJc2lTest</test>
<test>org.gwtproject.timer.client2.**</test>
</tests>
The timeout for each test not the entire suite in seconds (classpathscope=test
).
<test-timeout>60</test-timeout>
This parameter controls size of the thread pool used to execute parallel dependency processing. A value of 0, uses the CPU core * 2, a value of 1 is useful to limit a single task at a time which makes for uninterrupted console messages at the cost of longer build times.
<thread-pool-size>0</thread-pool-size>
A variety of txt files that used by one or more tasks and typically appear somewhere in a source root.
An artifact that will provide *.class files and will be added to the classpath of several tasks:
- JAVAC_COMPILE
- JAVAC_COMPILE_GWT_INCOMPATIBLE_STRIPPED_JAVA_SOURCE
- TRANSPILE_JAVA_TO_JAVASCRIPT
There are several ways to mark an artifact:
- A file called
.walkingkooka-j2cl-maven-plugin-classpath-required.txt
in the root - content are ignored. - Adding the artifact maven coords to the maven task configuration
classpath-required
.
An ignored artifact will have its java source, class files and other files ignored.
There are several ways to ignore an artifact:
- A file called '
.walkingkooka-j2cl-maven-plugin-ignored-dependency.txt
' in the root - contents are ignored. - Adding the artifact maven coords to the maven task configuration
ignored-dependency
.
A text file called .walkingkooka-j2cl-maven-plugin-ignored-files.txt
in the root - with file paths or glob patterns
that will result in any matched files being ignored.
- Blank lines are ignored
- Lines beginning with HASH are considered to be comments and are ignored.
- All other lines are used to build a glob pattern, using the java snippet directly below
- No support is provided for escaping of any sort.
This ignore file is used during the tasks:
- JAVAC_COMPILE
- JAVAC_COMPILE_GWT_INCOMPATIBLE_STRIPPED_JAVA_SOURCE
- TRANSPILE_JAVA_TO_JAVASCRIPT
All other files will be compiled or transpiled.
# This is a comment and ignored. The following two blank lines are also ignored.
# The two glob patterns will ignore files in this and any sub directories.
IgnoredFile1.*
sub2/IgnoredFile2.*
A javascript source required artifact will contain javascript files that need processing by the Closure compiler.
There are several ways to ignore an artifact:
- A file called
.walkingkooka-j2cl-maven-plugin-javascript-source-required.txt
in the root - contents are ignored. - Adding the artifact maven coords to the maven task configuration
javascript-source-required
.
Shading is useful particularly when developing emulation of JRE that are not baked in. Shading is a useful feature that allows the source and class files for both the JRE and authored replacement to co-exist and be unit test together.
An example where shading is utilized is the replacement/emulation of java.util.Base64
with walkingkooka.j2cl.java.util.Base64
with tests that exercise the features by executing the same parameters against the inbuild .
The properties file content. This example will eventually change packages starting with example.java.util
to java.util
.
example.java.util=java.util
Note that java source and their matching class files are both shaded using the same rules.
The sample below shows an example of the source before task 5, after that completes, the package and type references will have the example removed.
package example.java.util;
class Base64 {
class Decoder {
}
class Encoder {
}
}
The source after shading.
package java.util;
class Base64 {
class Decoder {
}
class Encoder {
}
}
A text file called .walkingkooka-j2cl-maven-plugin-public-files.txt
with file paths or glob patterns that will copied
to the output directory.
- Blank lines are ignored
- Lines beginning with HASH are considered to be comments and are ignored.
- All other lines are used to build a glob pattern, using the java snippet directly below
- No support is provided for escaping of any sort.
This file is used during the tasks:
- OUTPUT_ASSEMBLE
The file below will copy the index.html and gif files to the ouptut directory.
# This is a comment and ignored. The two blank lines are also ignored.
# Any files that match the pattern below will be copied from the source.
index.html
images/*.gif
The build process involves transforming the parent project and dependencies including transitives from java into javascript, in reverse order. Reverse order here means that if the project is the root of the dependency tree, then for all operations to complete successfully dependencies that are leaves of this tree must be processed first. Once the leaves are completed successfully dependencies or the project only requiring them can be attempted. Eventually the only outstanding artifact or dependency is the project itself.
The plugin will create a separate directory for each artifact, using the maven coordinates and a HASH of all dependencies. This means any time a dependency changes for any reason, any artifacts that reference it will also change and they will be processed once more which is the desired so that changes are included in the final output. Processing a single dependency potentially involves numerous tasks, as each is performed a directory which includes a number prefix is created. These sub directories will include a log file including all output for that task along with further files and directories. These logs will be useful if anything goes wrong.
Every single task for every single artifact will have its own log file under its own task directory under the directory for that artifact named according to the scheme mentioned above.
Note that the directory for each task will only include an empty directory indicating the status or outcome of that particular task. Possible outcomes include
- !ABORTED
- !FAILED
- !SKIPPED
- !SUCCESSFUL
These are useful as a quick mechanism to find the individual failing task, with the log.txt
containing further
details.
The first task whenever a dependency processing begins is to compute the hash which is then combined with the maven coordinates and used to create a directory if one did not previously exist.
The hash task directory will also include a hash.txt
file which contains all the items used to produce the hash. The
contents are also useful as a reference to discover which other dependencies were required by this particular
dependency, note the order of this listing matches the order dependencies are declared in the POM in a depth first
ordering.
compile-source-root: annotations
compile-source-root: java
define: jre.checkedMode=DISABLED
define: jre.checks.checkLevel=MINIMAL
define: jsinterop.checks=DISABLED
dependencies-0: walkingkooka:j2cl-uber:jar:1.0-SNAPSHOT
dependencies-1: walkingkooka:j2cl-jre-java:jar:1.0-SNAPSHOT
dependencies-2: com.google.jsinterop:jsinterop-annotations:jar:2.0.0
dependencies-3: walkingkooka:j2cl-gwt-internal-annotations:jar:1.0-SNAPSHOT
dependencies-4: walkingkooka:jsinterop-base:jar:1.0-SNAPSHOT
dependencies-5: walkingkooka:j2cl-javac-bootstrap-classpath:jar:1.0-SNAPSHOT
dependencies-6: walkingkooka:j2cl-jre-javascript:jar:1.0-SNAPSHOT
dependencies-7: walkingkooka:j2cl-bootstrap-javascript:jar:jszip:1.0-SNAPSHOT
entry-points: app.app
formatting: PRETTY_PRINT
initial-script-filename: /Users/miroslav/repos-github/j2cl-maven-plugin/target/it-tests/formatting-pretty-print/target/j2cl-maven-plugin-it-formatting-pretty-print-1.0/walkingkooka-j2cl-maven-plugin-it-formatting-pretty-print.js
language-out: ECMASCRIPT5
level: ADVANCED_OPTIMIZATIONS
scope: RUNTIME
sources-kind: SRC
An attempt will be made to locate the sources jar and unpack if found. If no java source files (*.java
) are found the
original artifact itself will be unpacked over the first unpack. If no java source files are found in either the
remaining tasks will be aborted, otherwise the next task will be attemped trying to eventually transpile the unpacked
java to javascript.
The source extracted in task 2 will then be compiled by javac.
The goal of this task is to remove classes and class members such as methods or fields that have been marked with the
@Gwt-incompatible
annotation with the "output" directory of this task containing the final result AFTER these classes
and members have been removed. Most of this work is done by the Google JavaPreprocessor
.
This task also removes entire classes that have been matched by the ignore files mentioned above.
This task invokes javac on the output produced by task 4.
This task will execute if a .walkingkooka-j2cl-maven-plugin-shade.txt
file is present. All the mapped java source
files will be shaded so they appear in the new package.
This task will execute if a .walkingkooka-j2cl-maven-plugin-shade.txt
file is present. All the mapped class files will
be shaded so they appear in the new package. The files modified here will be the class files of the java source modified
in task 5.
This task accepts the output from task 4 and transpile that java source into javascript.
This is the final task and only run for the project, it uses the Closure compiler to produce the final javascript file( s).
A build results in all required dependencies as necessary creating a directory under the cache directory formed from
the artifact coords along with a hash of various attributes and dependencies. The content that appears in each of these
logs are is also printed to the console but with multiple threads running concurrently it might be confusing with interleved messages.
It might also be useful to set the threadpool-size=1
so messages are not mixed up with multiple threads writing output.
../walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb
All the tasks for each artifact are also given a directory and log with all debug statements. Each log file will only contain output for the owning task, concurrent tasks produce independent log files.
Each component will include several of the tasks mentioned in the previous section, and a log file will be present with messages and other output concerning that particular task.
walkingkooka:j2cl-maven-plugin-it-junit-test:jar:1.0-TRANSPILE
Directory
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/7-transpiled-java-to-javascript
Preparing...
Source path(s)
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/3-gwt-incompatible-stripped-source/output
J2clTranspiler
Parameters
Classpath(s)
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/com/google/jsinterop/jsinterop-annotations/2.0.0/jsinterop-annotations-2.0.0.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-bootstrap-javascript/1.0-SNAPSHOT/j2cl-bootstrap-javascript-1.0-SNAPSHOT-jszip.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-gwt-internal-annotations/1.0-SNAPSHOT/j2cl-gwt-internal-annotations-1.0-SNAPSHOT.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-javac-bootstrap-classpath/1.0-SNAPSHOT/j2cl-javac-bootstrap-classpath-1.0-SNAPSHOT.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-jre-java/1.0-SNAPSHOT/j2cl-jre-java-1.0-SNAPSHOT.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-jre-javascript/1.0-SNAPSHOT/j2cl-jre-javascript-1.0-SNAPSHOT.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-junit-annotations/1.0-SNAPSHOT/j2cl-junit-annotations-1.0-SNAPSHOT.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-junit-java/1.0-SNAPSHOT/j2cl-junit-java-1.0-SNAPSHOT.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-junit-javascript--jar--1.0-SNAPSHOT-69164038504dad959653fbc60320aade26f8e7a7/4-javac-gwt-incompatible-stripped-source/output
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-repo/walkingkooka/j2cl-junit-processor/1.0-SNAPSHOT/j2cl-junit-processor-1.0-SNAPSHOT.jar
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--jsinterop-base--jar--1.0-SNAPSHOT-564fba3536a58e77c2eb8a64b36c82064c1711a8/4-javac-gwt-incompatible-stripped-source/output
11 file(s)
*.java Source(s)
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/3-gwt-incompatible-stripped-source/output
javatests/test
JunitTest_Adapter.java
test
JunitTest.java StringValue.java
3 file(s)
*.native.js source(s)
0 file(s)
*.js source(s)
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/3-gwt-incompatible-stripped-source/output/javatests/test
JunitTest_AdapterSuite.js
1 file(s)
Output
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/7-transpiled-java-to-javascript/output
J2clTranspiler
0 Error(s)
0 Warnings(s)
0 Message(s)
Copy js to output
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/7-transpiled-java-to-javascript/output/javatests/test
JunitTest_AdapterSuite.js
1 file(s)
Output file(s) after copy
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/7-transpiled-java-to-javascript/output
javatests/test
JunitTest_Adapter$GoogTestCase$$Overlay.impl.java.js JunitTest_Adapter$GoogTestCase$$Overlay.java.js
JunitTest_Adapter$GoogTestCase$$Overlay.js.map JunitTest_Adapter$IThenable$$Overlay.impl.java.js
JunitTest_Adapter$IThenable$$Overlay.java.js JunitTest_Adapter$IThenable$$Overlay.js.map
JunitTest_Adapter.impl.java.js JunitTest_Adapter.java
JunitTest_Adapter.java.js JunitTest_Adapter.js.map
JunitTest_AdapterSuite.js
test
JunitTest.impl.java.js JunitTest.java
JunitTest.java.js JunitTest.js.map
StringValue.impl.java.js StringValue.java
StringValue.java.js StringValue.js.map
19 file(s)
Log file
/Users/miroslav/repos-github/88j2cl-maven-plugin/target/it-tests/junit-test/target/walkingkooka-j2cl-maven-plugin-cache/walkingkooka--j2cl-maven-plugin-it-junit-test--jar--1.0-db1ecd80f01db349f97454549ba798c71e4283fb/7-transpiled-java-to-javascript/log.txt
The image below contains two panel views, the left shows a directory tree showing the output directory showing all artifacts and some log files expanded, and the right shows a sample log file. The log shows a successful Closure compile build, with numerous warning level messages. All the parameters and paths to files are above the area of the log shown.
Samples of all the various files mentioned above are available under samples
The Maven POM fragment declares two dependencies which should provide the minimal required dependencies for an application.
<dependencies>
<dependency>
<groupId>walkingkooka</groupId>
<artifactId>j2cl-uber</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>walkingkooka</groupId>
<artifactId>j2cl-uber-test</artifactId>
<version>1.0-SNAPSHOT</version>
<scope>test</scope>
</dependency>
</dependencies>
Note that a dependency with a classifier=sources
will always be removed from the dependencies prior to actual task
processing.
A dependency that includes the following dependencies will have the second automatically removed.
<dependencies>
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
<classifier>sources</classifier>
</dependency>
</dependencies>
Suggestions via the issue tracker, and pull requests are most welcomed.