Thursday, July 30, 2020

Content Reigns King, But That's Not Where the Power Lies

Slow Ventures Snail Mail

Thursday, July 30th, 2020

Welcome to another edition of Snail Mail! Today we're diving into celebrity platforms.

The rise of celebrity and influencer platforms like Community and Cameo clearly demonstrate demand for applications that facilitate interactions with talent. While there is good reason to be excited by applications that provide that interaction, we ultimately think that market size concerns and reliance on novelty to drive purchase decisions make it hard to bet on who winds up being the winner, though we know there's likely to be one. The better place to make a bet here is at the platform layer, where you can build for either side (i.e. fans or talent).

Content is still king, and the users, engagement and willingness to spend are all there. But rather than chase the new medium of engagement, the biggest opportunities in this space lie in building the picks and shovels that will help better monetize the talented.

Got forwarded this and want to subscribe? Go to https://slow.claims.

If Content is King, Build Tools for the Creators

"Content is king."

In 1996, Bill Gates published a letter while at Microsoft claiming that, "Content is where I expect much of the real money will be made on the Internet, just as it was in broadcasting." People across businesses and industries subscribed to the idea – that content would drive value creation on platforms.

In many ways, this has proven true. Platforms like Instagram, Twitter and Snapchat have provided talent with the infrastructure to build and connect directly with their fan bases, expanding what entertainment could be and redefining what it means to be considered a celebrity. Celebrities are no longer just movie stars, pop stars and athletes – today they include Instagram and TikTok stars, Twitter personalities, and anyone else with a following of a few thousand people. Technology eliminated gatekeepers and made distribution of content easier, and as a result, celebrities and influencers don't just provide entertainment, but they are also sought out for opinions on current events, advice and product recommendations.

This shift in fan expectation led to a wave of applications that provided new mediums for fan engagement. Text with Kerry Washington on Community, have Carole Baskin wish your brother happy birthday on Cameo, or get beauty tips on Supergreat. These platforms provide a home for large, engaged and somewhat homogenous userbases (at least from the standpoint that they each have a common interest), and by extension, allow celebrities to more easily monetize fan interaction.

Interest in these applications is not new, but has been invigorated with social distancing measures accompanying the arrival of COVID-19. For the past two years, startups have raised at massive valuations, riding the wave of interest: Community raised its Seed at $80M pre-money (May 2019), Cameo's Series B at $300M post-money (June 2019), and most recently, Clubhouse raised its Seed at $100M post-money (May 2020). Aggressive valuations were supported by user and eyeball counts, and in the lion's share of cases, followed platforms looking to build a new or better medium fan interaction.

But like all marketplaces and platforms, celebrity platforms still rely on two distinct groups: celebrities and their fans. And as with any platform, the question becomes, who do you build for? Do you build a fan-focused application, hoping to create a better or new medium for interaction? Or do you build infrastructure, focused on the talent and providing them the tools to better monetize themselves?

Fan Focused Applications

Fan focused applications are built to provide a new or better way to facilitate, broadly defined, fan engagement. The focus here is the interaction, which also serves as the point of monetization. These platforms charge for the ability to interact with celebrities: pay for a Cameo, advertise on a livestream, or take a cut of the e-commerce transaction.

The variety of monetization options, and the fact that fan bases are so engaged and willing to spend, is largely what has caused excitement in the space. More intimate fan interactions have brought fans onto these platforms, capturing eyeballs and users, and ultimately driving valuations.

But the very thing that has caused these platforms to grow so rapidly is the thing that makes their sustainability so questionable. Because novelty value drives the purchase decision in most of these applications, and that novelty value is created by its "newness" or differentiation, it brings into question their long-term viability. While novelty value can lead to sustained behavior over time, that's a big bet to make. Investors are therefore reliant on applications to either successfully change consumer behavior or to continuously innovate and develop new mediums of interaction, in order to keep users on the platform and justify bullish valuations.

Talent Focused Infrastructure

Alternatively, platforms built to enable and serve the needs of the talent offer different long term value as a business. Rather than focusing on the point of interaction between celebrities and their fans, these platforms are built to provide business infrastructure to celebrities that can help them to better monetize.

These 'businesses in a box' can take a number of forms, from allowing individuals to better control their fans' data to providing e-commerce infrastructure that allows them to more easily sell products online to providing platforms that allow celebrities to host digital events. In each of these instances, the major difference is that they're providing a service to the talent, thus capturing them as the payor.

In contrast to fan focused platforms, building tools for the talent creates a less flashy, but arguably more sustainable business. With repeat purchase driven by the value provided to the talent, these platforms remain valuable regardless of what the newest app is or the ebb and flow of fan/consumer preferences.

Concern around talent focused infrastructure, rather, centers primarily on size of the market. Market size concerns are based on two different considerations: first, whether or not products will need to be verticalized to such an extent that they won't be broadly attractive, and second, whether or not these services are only valuable to smaller celebrities who can't afford to build out tools themselves. Despite these concerns, we're confident that the total addressable market is large enough, specifically believing that while the initial cohort may have smaller followings, individuals who start on these platforms will not abandon them once they reach scale.

So What's This All Mean?

We started looking at celebrity and influencer platforms largely because there's so much activity, and a lot of smart people involved. Usually when that's the case, there's something there, we just didn't know what. We focused on product and applications because that's where the most people seemed to be: Who had the best talent roster? Which product was the least reliant on novelty? And how were they assuring that they'd keep the talent on the platform?

We started chatting with friends and builders in the space, and in those conversations, two things emerged: first, our initial concerns around the importance of novelty in driving adoption were, at minimum, recognized by all, and second, we'd completely ignored the point of view of the talent, the group that we'd deemed most important to the success of these platforms.

It quickly became clear that platforms could be built to provide talent with more than just a way to monetize direct interaction and that the race to capture eyeballs and users had left the business tools these individuals needed woefully underdeveloped. By building a platform that serves the needs of talent, the talent becomes the customer, and revenue becomes smoother and recurring.

So where'd we wind up after all of this? We know that while fan demand exists for applications that facilitate talent interactions, concerns around the size of the market and reliance on novelty to drive purchase decisions makes it hard to bet on who's going to successfully build long-term enterprise value (but we believe that someone will!). Rather, we're excited by founders who are building infrastructure that empowers talent to run their businesses. We believe that these platforms can generate smooth, recurring revenue, and that there are a few ways to do this.

We want to see someone build Salesforce (and Shopify!) for celebrities. There's still limited ways for talent to collect, organize and use data and information on their fan bases, and empowering them to better target and engage with their following would create real, sustainable value. We also believe that this product would provide real value to groups well-beyond celebrities. As technology has enabled talented people across industries to go direct-to-consumer, we see the opportunity to build platforms for individuals and SMBs in every expertise-driven business (e.g. actors, musicians, comedians, doctors, psychiatrists, financial advisors, etc.).

Content is still king, and the users, engagement and willingness to spend are all there. So rather than chase the new medium of engagement, we're executed by the opportunity to build the picks and shovels that will help talent to better monetize themselves.

Want moar? Check us out on:
Facebook, Twitter, Medium or our Website

Signup for Snail Mail Newsletters at http://slow.claims

Our mailing address is:
1006 Kearny St, San Francisco, CA 94133

Don't Want These Emails?
unsubscribe from this list

Donate BTC: 3BJW4B6GGpoQrjeom6RpVtkza3XPw2qjoK
Donate ETH: 0xD7599b3D15805aDF3144676914964e8fff53C925

Wednesday, July 29, 2020

Re: How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

Reads like your war file is empty.

You *must* declare your dependencies via Gradle and if you are mixing server and client code, (a really bad idea), together you will need to remove the root spec exclude filters.

On Wed, Jul 29, 2020 at 9:15 AM mb user <muser071@gmail.com> wrote:

Thank You Michael!

It was a big help.

Except the :farmRun I can successfully execute the commands.

:farmRun give me an interesting "java.util.zip.ZipException: zip file is empty" message. Any idea, what is this?

Full log:

gradlew :farmRun
j├║l. 29, 2020 3:07:27 DU org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-8080"]
j├║l. 29, 2020 3:07:32 DU org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Tomcat]
j├║l. 29, 2020 3:07:32 DU org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet engine: [Apache Tomcat/9.0.34]
j├║l. 29, 2020 3:07:32 DU org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@395b56bb]
        at java.util.concurrent.FutureTask.report(FutureTask.java:122)
        at java.util.concurrent.FutureTask.get(FutureTask.java:192)
        at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
        at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
        at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
        at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
        at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.startup.Tomcat.start(Tomcat.java:468)
        at org.apache.catalina.startup.Tomcat$start$0.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:119)
        at org.akhikhl.gretty.TomcatServerManager.startServer(TomcatServerManager.groovy:52)
        at org.akhikhl.gretty.ServerManager$startServer$0.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:127)
        at org.akhikhl.gretty.Runner.run(Runner.groovy:129)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.runtime.callsite.PlainObjectMetaMethodSite.doInvoke(PlainObjectMetaMethodSite.java:43)
        at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:190)
        at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:70)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:119)
        at org.akhikhl.gretty.Runner.main(Runner.groovy:54)
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@395b56bb]
        at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:173)
        at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:727)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4805)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4940)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
        at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
        at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
        ... 36 more
Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: zip file is empty
        at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:143)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
        ... 48 more
Caused by: java.util.zip.ZipException: zip file is empty
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:225)
        at java.util.zip.ZipFile.<init>(ZipFile.java:155)
        at java.util.jar.JarFile.<init>(JarFile.java:166)
        at java.util.jar.JarFile.<init>(JarFile.java:130)
        at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:184)
        at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:169)
        at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:140)
        ... 49 more

On Tuesday, July 28, 2020 at 8:51:02 PM UTC+2, Michael Joyner wrote:

We use a build.gradle file similar to the following for most of our GWT client projects:

(Note: We use './gradlew :gwts' to run SDM and './gradlew :build :farmRun' to run a local http server)

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6ca14730-9480-49d1-b9b6-782f7d8bd539o%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAFHWztxPRo%2BXzdNdDxhdUoQwakhctXAcmSdR9oRxu83JNWxTCw%40mail.gmail.com.

Re: How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

Thank You Michael!

It was a big help.

Except the :farmRun I can successfully execute the commands.

:farmRun give me an interesting "java.util.zip.ZipException: zip file is empty" message. Any idea, what is this?

Full log:

gradlew :farmRun
j├║l. 29, 2020 3:07:27 DU org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-8080"]
j├║l. 29, 2020 3:07:32 DU org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Tomcat]
j├║l. 29, 2020 3:07:32 DU org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet engine: [Apache Tomcat/9.0.34]
j├║l. 29, 2020 3:07:32 DU org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@395b56bb]
        at java.util.concurrent.FutureTask.report(FutureTask.java:122)
        at java.util.concurrent.FutureTask.get(FutureTask.java:192)
        at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
        at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
        at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
        at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
        at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.startup.Tomcat.start(Tomcat.java:468)
        at org.apache.catalina.startup.Tomcat$start$0.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:119)
        at org.akhikhl.gretty.TomcatServerManager.startServer(TomcatServerManager.groovy:52)
        at org.akhikhl.gretty.ServerManager$startServer$0.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:127)
        at org.akhikhl.gretty.Runner.run(Runner.groovy:129)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.runtime.callsite.PlainObjectMetaMethodSite.doInvoke(PlainObjectMetaMethodSite.java:43)
        at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:190)
        at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:70)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:119)
        at org.akhikhl.gretty.Runner.main(Runner.groovy:54)
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@395b56bb]
        at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:173)
        at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:727)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4805)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4940)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
        at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
        at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
        at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
        ... 36 more
Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: zip file is empty
        at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:143)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
        ... 48 more
Caused by: java.util.zip.ZipException: zip file is empty
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:225)
        at java.util.zip.ZipFile.<init>(ZipFile.java:155)
        at java.util.jar.JarFile.<init>(JarFile.java:166)
        at java.util.jar.JarFile.<init>(JarFile.java:130)
        at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:184)
        at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:169)
        at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:140)
        ... 49 more

On Tuesday, July 28, 2020 at 8:51:02 PM UTC+2, Michael Joyner wrote:

We use a build.gradle file similar to the following for most of our GWT client projects:

(Note: We use './gradlew :gwts' to run SDM and './gradlew :build :farmRun' to run a local http server)

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6ca14730-9480-49d1-b9b6-782f7d8bd539o%40googlegroups.com.

Tuesday, July 28, 2020

Re: How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

We use a build.gradle file similar to the following for most of our GWT client projects:

(Note: We use './gradlew :gwts' to run SDM and './gradlew :build :farmRun' to run a local http server)

apply plugin: 'java'
apply plugin: 'war'
apply plugin: 'gwt'
apply plugin: 'eclipse'
apply plugin: 'eclipse-wtp'
apply plugin: 'org.gretty'
apply plugin: 'maven'

sourceCompatibility = JavaVersion.VERSION_1_8
targetCompatibility = JavaVersion.VERSION_1_8

if (JavaVersion.current() > JavaVersion.VERSION_1_8) {
    tasks.withType(JavaCompile) {
        options.compilerArgs.addAll(["--release", "8"])
    }
}

compileJava.options.encoding = 'UTF-8'
compileTestJava.options.encoding = 'UTF-8'

farm {
webapp ':'
}

buildscript {
    repositories {
        jcenter()
        maven { url 'https://repo.spring.io/plugins-release' }
        maven { url "https://plugins.gradle.org/m2/" }
        maven { url 'https://jitpack.io' }
    }
    dependencies {
        classpath 'org.wisepersist:gwt-gradle-plugin:1.+'
        classpath "gradle.plugin.org.gretty:gretty:3.0.3"
    }
}

war {
    archiveName 'client.war'
    rootSpec.exclude('WEB-INF/classes/**/*.class')
    rootSpec.exclude('WEB-INF/classes/**/*.gwt.xml')
}

gretty {
    httpPort = 8080;
    servletContainer = 'tomcat9'
    managedClassReload = false
    reloadOnClassChange = false
    extraResourceBase 'build/gwt/out'
    jvmArgs = ['-Dfile.encoding=UTF-8', '-Xmx2048M', '-Ddebug=true' ]
    redeployMode='redeploy'
}

repositories {
    jcenter()
    maven { url 'https://jitpack.io' }
}

gwt {
    logLevel = 'INFO'

    maxHeapSize = "8192M";

    //gwtVersion='2.8.2'
    gwtVersion='2.9.0'

    modules 'com.project.Module'

    compiler {
        disableClassMetadata = false;
        strict = true;
        style = "OBF";
        //style = "PRETTY";
        localWorkers = 4;
    }

    superDev {
        noPrecompile = true;
        failOnError = false;
        bindAddress = "0.0.0.0";
    }

    eclipse {
        addGwtContainer = true;
    }
}

configurations {
provided
}

dependencies {
    gwt 'com.google.gwt:gwt-user:'+gwt.gwtVersion
    providedCompile 'com.google.gwt:gwt-servlet:'+gwt.gwtVersion

    gwt 'com.google.elemental2:elemental2-dom:1.0.0'
    gwt 'com.google.elemental2:elemental2-core:1.0.0'
    gwt 'com.google.elemental2:elemental2-promise:1.0.0'
    gwt 'com.ekotrope:gwt-completablefuture:1.0.0'

    providedCompile 'javax.servlet:javax.servlet-api:3.0.1'
    compile 'javax.ws.rs:javax.ws.rs-api:2.1.1'

    gwt 'org.fusesource.restygwt:restygwt:2.2.+'
    gwt "com.fasterxml.jackson.core:jackson-annotations:2.9.6"
    gwt "com.fasterxml.jackson.core:jackson-databind:2.9.6"
    gwt 'com.google.code.findbugs:jsr305:3.0.0' //required for restygwt compile
    gwt 'com.github.nmorel.gwtjackson:gwt-jackson:0.15.2'

    gwt ('com.google.gwt.eventbinder:eventbinder:1.1.0') {
        //exclude module: 'gwt-user'
    }

    gwt 'javax.xml.bind:jaxb-api:2.3.+'
}

task "create-dirs" {
    doLast{
    sourceSets*.java.srcDirs*.each { it.mkdirs() }
    sourceSets*.resources.srcDirs*.each { it.mkdirs() }
}}

eclipseJdt {
    doLast{
    File f = file('.settings/org.eclipse.core.resources.prefs')
    f.write('eclipse.preferences.version=1\n')
    f.append('encoding/<project>=utf-8')
    f = file('.settings/org.eclipse.core.runtime.prefs')
    f.write('eclipse.preferences.version=1\n')
    f.append('line.separator=\\n\n')
}}

eclipse {
    project {
        name = 'My Project'
        webAppDirName = 'src/main/webapp'
    }

    classpath {
        downloadSources = true
        downloadJavadoc = true
    }

    jdt {
        sourceCompatibility=1.8
        targetCompatibility=1.8
    }

    wtp {
        facet {
            facets = []
            facet name: 'jst.java', version: '1.8'
            facet name: 'jst.web', version: '3.0'
            facet name: 'com.gwtplugins.gwt.facet', version: '1.0'
        }
    }
}

On 7/28/20 1:53 PM, mb user wrote:

I imported the project from svn, then eclipse created a new gradle project.

It seems like gradle recognize this project as a normal java project.

I have only src and war directories in the repository, so no files in the root dir.

In the src there are numerous gwt modules directories, and in the war, there are html/css static files for gwt modules and in the WEB-INF dir:

c:\p\eclipse\fejlesztoi2>dir /b /s "war/WEB-INF"
c:\p\eclipse\fejlesztoi2\war\WEB-INF\glassfish-web.xml
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib
c:\p\eclipse\fejlesztoi2\war\WEB-INF\web.xml
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\activation.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\commons-fileupload-1.2.1.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gchart.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-ajaxloader.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-maps-api-3.10.0-alpha-8-SNAPSHOT.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-servlet.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\javax.xml.soap-api-1.4.0.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\mail.jar

what's next?

On Tuesday, July 28, 2020 at 5:46:07 PM UTC+2, Michael Conrad wrote:

Use Maven or Gradle to configure the project and let Eclipse import it as a Maven or Gradle project.

On Tue, Jul 28, 2020 at 11:42 AM mb user <muse...@gmail.com> wrote:

Hi,

After a storage crash, I had to reinstall my development computer.

Now I have eclipse 4.16 and a gwt 2.8.1 project source imported from svn.

This project was built with the eclipse gwt plugin, but I cannot install it to eclipse 4.16.

What is the recommended way to achieve compile and deploy (create war file) in eclipse, if you have the project source?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b10ca891-b6d0-4fdf-a2ee-e0296cb03fc2o%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/60e9fd36-d19e-400b-905a-19f8ba068d16o%40googlegroups.com.

Re: How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

I imported the project from svn, then eclipse created a new gradle project.

It seems like gradle recognize this project as a normal java project.

I have only src and war directories in the repository, so no files in the root dir.

In the src there are numerous gwt modules directories, and in the war, there are html/css static files for gwt modules and in the WEB-INF dir:

c:\p\eclipse\fejlesztoi2>dir /b /s "war/WEB-INF"
c:\p\eclipse\fejlesztoi2\war\WEB-INF\glassfish-web.xml
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib
c:\p\eclipse\fejlesztoi2\war\WEB-INF\web.xml
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\activation.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\commons-fileupload-1.2.1.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gchart.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-ajaxloader.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-maps-api-3.10.0-alpha-8-SNAPSHOT.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-servlet.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\javax.xml.soap-api-1.4.0.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\mail.jar

what's next?

On Tuesday, July 28, 2020 at 5:46:07 PM UTC+2, Michael Conrad wrote:

Use Maven or Gradle to configure the project and let Eclipse import it as a Maven or Gradle project.

On Tue, Jul 28, 2020 at 11:42 AM mb user <muse...@gmail.com> wrote:
Hi,

After a storage crash, I had to reinstall my development computer.

Now I have eclipse 4.16 and a gwt 2.8.1 project source imported from svn.

This project was built with the eclipse gwt plugin, but I cannot install it to eclipse 4.16.

What is the recommended way to achieve compile and deploy (create war file) in eclipse, if you have the project source?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b10ca891-b6d0-4fdf-a2ee-e0296cb03fc2o%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/60e9fd36-d19e-400b-905a-19f8ba068d16o%40googlegroups.com.

Re: How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

Use Maven or Gradle to configure the project and let Eclipse import it as a Maven or Gradle project.

On Tue, Jul 28, 2020 at 11:42 AM mb user <muser071@gmail.com> wrote:

Hi,

After a storage crash, I had to reinstall my development computer.

Now I have eclipse 4.16 and a gwt 2.8.1 project source imported from svn.

This project was built with the eclipse gwt plugin, but I cannot install it to eclipse 4.16.

What is the recommended way to achieve compile and deploy (create war file) in eclipse, if you have the project source?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b10ca891-b6d0-4fdf-a2ee-e0296cb03fc2o%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAFHWztyMZY2ozMHTkBnCDs2m0fuqLPWzXFV4VhbEODYT%3D3wvVQ%40mail.gmail.com.

How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

Hi,

After a storage crash, I had to reinstall my development computer.

Now I have eclipse 4.16 and a gwt 2.8.1 project source imported from svn.

This project was built with the eclipse gwt plugin, but I cannot install it to eclipse 4.16.

What is the recommended way to achieve compile and deploy (create war file) in eclipse, if you have the project source?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b10ca891-b6d0-4fdf-a2ee-e0296cb03fc2o%40googlegroups.com.

Re: Do Google Web Toolkit's touch events support Windows tablets?

When I looked at this 6 years ago (in relation to MGWT, which is dead although we still use it in legacy products) Pointer events were the way to go and are supported on all browsers now as far as I am aware.

There was talk of a single touch/pointer API system in GWT similar to what MGWT did where it took mouse, touch and pointer events and converted to a single touch event system. Hence you coded to MGWT's touch system and it worked on all devices.

No idea if GWT did this in the end.

I assume you are using an old IE Edge? Latest Edge uses webkit under the hood and so your problems may go away with this browser. Older IE Edge as far as I can remember does not support touch events but does support Pointer events.

Take what I say with a pinch of salt. It has been many years but I believe that is why you have an issue.

On Tue, 28 Jul 2020 at 07:37, Frank <frank.wynants@gmail.com> wrote:

Maybe you can Google for : JS surface touch events
Or something like that. But for JS. Maybe that can point you in the right direction.
Op maandag 27 juli 2020 om 22:02:20 UTC+2 schreef m.conr...@gmail.com:
you will need to check and see what event is actually generated for the windows 10 tablet in the dom and hook those.

On Mon, Jul 27, 2020 at 2:52 PM Andy Langer <mighty...@gmail.com> wrote:
Hi all. Currently working on a webapp using GWT. I currently have a feature working with touch events on a Canvas. The feature itself works perfectly fine on every device but windows tablets (surface pro). Is there something special I have to do for this, or does GWT have no way of doing this?

--
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 google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/940db851-82c2-4f1a-99b8-8ef653d1dadao%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/af7c625a-85ef-4e21-95e3-8520bbc7d10cn%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABia8q4zDi6Lcjc%2BxuF7233V8ohtaaZ8BQWbEuULMEDBVsGS6w%40mail.gmail.com.

Monday, July 27, 2020

Re: Do Google Web Toolkit's touch events support Windows tablets?

Maybe you can Google for : JS surface touch events
Or something like that. But for JS. Maybe that can point you in the right direction.

Op maandag 27 juli 2020 om 22:02:20 UTC+2 schreef m.conr...@gmail.com:

you will need to check and see what event is actually generated for the windows 10 tablet in the dom and hook those.

On Mon, Jul 27, 2020 at 2:52 PM Andy Langer <mighty...@gmail.com> wrote:
Hi all. Currently working on a webapp using GWT. I currently have a feature working with touch events on a Canvas. The feature itself works perfectly fine on every device but windows tablets (surface pro). Is there something special I have to do for this, or does GWT have no way of doing this?

--
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 google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/940db851-82c2-4f1a-99b8-8ef653d1dadao%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/af7c625a-85ef-4e21-95e3-8520bbc7d10cn%40googlegroups.com.

Re: Is there any way to use GWT 2.9 with Java 11 using Eclipse GWT plugin?

Thanks for the prompt response.

The issue is the internal Jetty that cannot be loaded with openJdk 11. Here is the log.

Is there any way to replace the internal Jetty with a higher version? I Checked the Jetty forum and apparently they are aware of this.

The code server is ready at http://127.0.0.1:9876/

Code server started in 20.11 s ms

[ERROR] jreLeakPrevention.gcDaemonFail

java.lang.ClassNotFoundException: sun.misc.GC

at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)

at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)

at java.base/java.lang.Class.forName0(Native Method)

at java.base/java.lang.Class.forName(Class.java:315)

at com.google.gwt.dev.shell.jetty.JettyLauncher.jreLeakPrevention(JettyLauncher.java:899)

at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:722)

at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)

at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898)

at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705)

at com.google.gwt.dev.DevMode.main(DevMode.java:432)

2020-07-27 15:36:29.138:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT

Starting Jetty on port 8888

[WARN] Failed startup of context c.g.g.d.s.j.WebAppContextWithReload@8953a7d{/,file:/C:/Eclipse_WP_Java11/Rguroo/war/,STARTING}{C:\Eclipse_WP_Java11\Rguroo\war}

MultiException[java.lang.RuntimeException: Error scanning file Rguroo$1.class, java.lang.RuntimeException: Error scanning file Rguroo$1MyHandler$1.class, java.lang.RuntimeException: Error scanning file Rguroo$1MyHandler.class, java.lang.RuntimeException: Error scanning file Rguroo.class]

at org.eclipse.jetty.annotations.AnnotationConfiguration.scanForAnnotations(AnnotationConfiguration.java:536)

at org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:447)

at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:479)

at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1337)

at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)

at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)

at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:550)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)

at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)

at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)

at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)

at org.eclipse.jetty.server.handler.RequestLogHandler.doStart(RequestLogHandler.java:140)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)

at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)

at org.eclipse.jetty.server.Server.start(Server.java:387)

at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)

at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)

at org.eclipse.jetty.server.Server.doStart(Server.java:354)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)

at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:760)

at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)

at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898)

at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705)

at com.google.gwt.dev.DevMode.main(DevMode.java:432)

Caused by: MultiException[java.lang.RuntimeException: Error scanning file Rguroo$1.class, java.lang.RuntimeException: Error scanning file Rguroo$1MyHandler$1.class, java.lang.RuntimeException: Error scanning file Rguroo$1MyHandler.class, java.lang.RuntimeException: Error scanning file Rguroo.class]

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:681)

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:688)

at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:824)

at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)

at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)

at java.base/java.lang.Thread.run(Thread.java:834)

Suppressed: java.lang.RuntimeException: Error scanning file Rguroo$1MyHandler$1.class

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:708)

... 10 more

Caused by: java.lang.UnsupportedOperationException: This feature requires ASM7

at org.objectweb.asm.ClassVisitor.visitNestHost(ClassVisitor.java:150)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:550)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:702)

... 10 more

Suppressed: java.lang.RuntimeException: Error scanning file Rguroo$1MyHandler.class

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:708)

... 10 more

Caused by: java.lang.UnsupportedOperationException: This feature requires ASM7

at org.objectweb.asm.ClassVisitor.visitNestHost(ClassVisitor.java:150)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:550)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:702)

... 10 more

Suppressed: java.lang.RuntimeException: Error scanning file Rguroo.class

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:708)

... 10 more

Caused by: java.lang.UnsupportedOperationException: This feature requires ASM7

at org.objectweb.asm.ClassVisitor.visitNestMember(ClassVisitor.java:236)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:660)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:702)

... 10 more

Caused by: java.lang.RuntimeException: Error scanning file Rguroo$1.class

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:708)

... 10 more

Caused by: java.lang.UnsupportedOperationException: This feature requires ASM7

at org.objectweb.asm.ClassVisitor.visitNestHost(ClassVisitor.java:150)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:550)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:702)

... 10 more

2020-07-27 15:36:31.285:INFO:oejs.ServerConnector:main: Started ServerConnector@21421b3{HTTP/1.1}{127.0.0.1:8888}

2020-07-27 15:36:31.285:INFO:oejs.Server:main: Started @23499ms

On Monday, July 27, 2020 at 3:42:13 PM UTC-7 m.conr...@gmail.com wrote:

I use Gradle to configure Eclipse.
For JDK11 to be used as if it were JDK8 in Eclipse I have added:

sourceCompatibility = JavaVersion.VERSION_1_8
targetCompatibility = JavaVersion.VERSION_1_8
if (JavaVersion.current() > JavaVersion.VERSION_1_8) {
tasks.withType(JavaCompile) {
options.compilerArgs.addAll(["--release", "8"])
}
}

On Mon, Jul 27, 2020 at 6:12 PM Shahram Zadeh <shahra...@gmail.com> wrote:
We have a huge GWT project (GWT 2.7, JDK 1.7, Eclipse) everything works perfect. We are planning to upgrade to Java 11 and GWT 2.9 which has been recently released. However Java 1.7 is retiring and getting obsolete we have to move on and upgrade. Since last week we are trying to create a development environment like the existing one but there is no success. I was wondering whether anyone out there is struggling with the same issue, any hint, solution or hacking the eclipse plugin would be greatly appreciated.
Eclipse plugin comes with GWT (2.7 and 2.8.1)

--
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 google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1bdedb59-090d-4c8c-ba72-258e991ae060n%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/29f63cba-e8ed-44fa-867c-edbad082e366n%40googlegroups.com.