Thanks for the comment.
I don't think that we can say that Gradle will remove Maven in the future,
since Maven is also still in development.
For many reasons it is also easier to stay with Maven. Not every projects
have a high requirement for build process. So IMHO Maven is still the
simplest
We have seen similar issues with this when we were experimenting with some
projects and upgrading to 2.8.2. The things to double check are:
1. That there are no duplicate jars from different versions of GWT, as
mentions by Thomas Broyer.
2. Delete any GWT generated folder such as the
Nice article, thanks for sharing it.
I wonder if it's time to move from maven to gradle (in general and also
talking specifically about GWT Boot).
On Wednesday, May 23, 2018 at 2:24:14 PM UTC-5, Dr. Lofi Dewanto wrote:
>
> This article is now being published by DZone: *http://bit.ly/2IICra8
>
I sometimes, when I'm a bit desperate, I debug the project, find some
classes for the conflicting code using the
"Thread.currentThread().getContextClassLoader().loadClass(...)", and use
the variable inspector to find the class loader and the actual file that
has been used to load the class.
Hi,
I also think that Maven is not a bad choice for the most of projects and
personally use it for all my projects. But support the Gradle is not a bad
idea :)
If you need more information about GWT + Gradle you can ask Thomas Broyer,
as I know he is a big enthusiast of the Gradle.
Stas
On
I am :-)
Though I have very limited experience with GWT and Gradle.
--
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
