New Gradle plugin for GWT available

[esoco GmbH]

Because both existing Gradle plugins for GWT are no longer maintained I
forked the most recent of these (previously known as *putnami-gradle-plugin*)
and released the most recent code with a few improvements. The new plugin
also supports the current GWT Eclipse plugin so that it can be used
together with the Gradle *eclipse* plugin. The new plugin is available on
GitHub:

https://github.com/esoco/gwt-gradle-plugin

The most recent version is 1.0.2, released yesterday. Although the names
are identical the new plugin should not be confused with the older and even
longer unmaintained *gwt-gradle-plugin* by Steffen Schaefer on GitHub. The
configuration syntax is inherited from the more recent *Putnami* plugin,
only have the plugin and task names been changed to the more appropriate
*gwt*. Please check the GitHub page for details.

Feedback and contributions are welcome.

[Hristo Stoyanov]

Are you using this plugin yourself and do you plan on developing with GWT in the long run?

The other plugins were abondended becuase their authors moved on.

Congrats!

[esoco GmbH]

Yes, I'm using the plugin (that was the main reason for forking it) and are
also still using GWT. It's difficult to tell about the long run but given
the mature and stable Java environment I still see GWT as a good solution
to create web applications, especially ones that need to be maintained for
some time. Not everything in the software business is "fire and forget" :-)

[Michael Joyner]

Which plugin?

Post by esoco GmbH
Yes, I'm using the plugin (that was the main reason for forking it)
and are also still using GWT. It's difficult to tell about the long
run but given the mature and stable Java environment I still see GWT
as a good solution to create web applications, especially ones that
need to be maintained for some time. Not everything in the software
business is "fire and forget" :-)
--
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
To post to this group, send email to
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[esoco GmbH]

See first post in this thread.

Post by Michael Joyner
Which plugin?

[Michael Joyner]

Which isn't in my inbox.

Post by esoco GmbH
See first post in this thread.
Which plugin?

[Hristo Stoyanov]

Good to hear, I will give it a try!

[salk31]

"*maintained for some time*" at the risk of being off topic, so nice to
hear this. I have to have the argument about why we not using the latest
JavaScript (or variant of) framework so often. During the life of my
current project this has included saying why we are not using Angular 1,
then why not Angular 2 and now React.

Thanks and sorry for butting in!

Post by esoco GmbH
Yes, I'm using the plugin (that was the main reason for forking it) and
are also still using GWT. It's difficult to tell about the long run but
given the mature and stable Java environment I still see GWT as a good
solution to create web applications, especially ones that need to be
maintained for some time. Not everything in the software business is "fire
and forget" :-)

[Олег Рачаев]

great! I am using putnami gradle plugin.

Please see my patch to work with embedded tomcat server in Eclipse IDE
https://groups.google.com/forum/#!searchin/Google-Web-Toolkit/putnami%7Csort:date/google-web-toolkit/QPw1YbUdCM4/E2Dj-rjNBAAJ

втПрМОк, 18 сеМтября 2018 г., 12:00:06 UTC+4 пПльзПватель esoco GmbH

Post by esoco GmbH
Because both existing Gradle plugins for GWT are no longer maintained I
forked the most recent of these (previously known as
*putnami-gradle-plugin*) and released the most recent code with a few
improvements. The new plugin also supports the current GWT Eclipse plugin
so that it can be used together with the Gradle *eclipse* plugin. The new
https://github.com/esoco/gwt-gradle-plugin
The most recent version is 1.0.2, released yesterday. Although the names
are identical the new plugin should not be confused with the older and even
longer unmaintained *gwt-gradle-plugin* by Steffen Schaefer on GitHub.
The configuration syntax is inherited from the more recent *Putnami*
plugin, only have the plugin and task names been changed to the more
appropriate *gwt*. Please check the GitHub page for details.
Feedback and contributions are welcome.

[Thad Humphries]

Thank you. This arrives in the nick of time. I've been using the Schaefer
plugin for years, but now that customers have *finally* upgraded from Java
6, I'm updating to GWT 2.8.2, Java 8, and looking at Java 11 (tried Java
9/Jigsaw over a year ago, and the only changes I had were server side to
drop Java Advanced Imaging now that Java itself support TIFF).

Post by esoco GmbH
Because both existing Gradle plugins for GWT are no longer maintained I
forked the most recent of these (previously known as
*putnami-gradle-plugin*) and released the most recent code with a few
improvements. The new plugin also supports the current GWT Eclipse plugin
so that it can be used together with the Gradle *eclipse* plugin. The new
https://github.com/esoco/gwt-gradle-plugin
The most recent version is 1.0.2, released yesterday. Although the names
are identical the new plugin should not be confused with the older and even
longer unmaintained *gwt-gradle-plugin* by Steffen Schaefer on GitHub.
The configuration syntax is inherited from the more recent *Putnami*
plugin, only have the plugin and task names been changed to the more
appropriate *gwt*. Please check the GitHub page for details.
Feedback and contributions are welcome.

[Thad Humphries]

Has something gone wrong with the plugin? Yesterday I was able to install
and use it. Today, on a different machine, I check out my project, and the
plugin cannot be found (see below). The line #18 in question is *id
'de.esoco.gwt' version '1.0.2'*, just as it says on the GitHub page. My
gradlew run Gradle 4.10.2.

$ ./gradlew clean

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/thad/experimental/webgwt282/build.gradle' line: 18

* What went wrong:
Error resolving plugin [id: 'de.esoco.gwt', version: '1.0.2']

Could not resolve all dependencies for configuration

'detachedConfiguration1'.

Could not determine artifacts for

de.esoco.gwt:de.esoco.gwt.gradle.plugin:1.0.2

Could not get resource

'https://plugins.gradle.org/m2/de/esoco/gwt/de.esoco.gwt.gradle.plugin/1.0.2/de.esoco.gwt.gradle.plugin-1.0.2.jar'.

Could not HEAD

'https://plugins.gradle.org/m2/de/esoco/gwt/de.esoco.gwt.gradle.plugin/1.0.2/de.esoco.gwt.gradle.plugin-1.0.2.jar'.

Read timed out

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 31s

Because both existing Gradle plugins for GWT are no longer maintained I
forked the most recent of these (previously known as
*putnami-gradle-plugin*) and released the most recent code with a few
improvements. The new plugin also supports the current GWT Eclipse plugin
so that it can be used together with the Gradle *eclipse* plugin. The new
https://github.com/esoco/gwt-gradle-plugin
The most recent version is 1.0.2, released yesterday. Although the names
are identical the new plugin should not be confused with the older and even
longer unmaintained *gwt-gradle-plugin* by Steffen Schaefer on GitHub.
The configuration syntax is inherited from the more recent *Putnami*
plugin, only have the plugin and task names been changed to the more
appropriate *gwt*. Please check the GitHub page for details.
Feedback and contributions are welcome.

[Олег Рачаев]

How can I setup JNDI params for this plugin's embeded Jetty ?

[esoco GmbH]

I've not used that feature much yet, but maybe similar as with the GWT
plugin's embedded Jetty: by using a jetty-web.xml in the WEB-INF?

Post by Олег Рачаев
How can I setup JNDI params for this plugin's embeded Jetty ?