Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    Thomas Broyer
    This all depends what kind of "UI state" you want/have to store, and whether it can be shared or not. E.g. the expanded/collapsed state of a tree probably doesn't need to be shared, and yet you might want it to survive page reloads. Same for form contents (possibly stored in local storage to survive longer than a refresh; I believe that's what GitHub does when you're writing a comment). But if there's a reason to "share it", or "bookmark it", then yes by all means put it in the URL.
    Dmitrii Tikhomirov
    To Whom It May Concern :) new release of xml jre/gwt/j2cl compatible mapper/marshaller https://github.com/treblereel/mapper-xml/releases/tag/mapper-parent-0.4
    Hi Everyone!! Guys you could please help me. I am trying to use lombok but when I try to compile I receive an error, the build can not identify the code generated by lombok. I am using maven and I am new in GWT. Do you what is going on? Thank you!!!
    Colin Alworth
    gwt can't use lombok out of the box - lombok generates new bytecode, while gwt reads the sources from your project instead of bytecode
    My app is using the GWT 2.8.2 version
    Colin Alworth
    that said, lombok has a jdt backend, and gwt uses jdt, so it is possible to load up lombok into gwt and ask it to run as gwt is working
    you must have some configuration like that in your gwt-maven-plugin setup for lombok to work in gwt
    Hum ok. I will take a look on that.
    Thank you.
    Colin Alworth
    if you inherited this project with lombok already added, it likely either has this, or didnt build before you got started (perhaps was only meant to build in an IDE? stranger things have happened...)
    Yes, I have inherited the project with lombok but they never used in GWT scope I think so.
    It was created 2 years ago
    and have to put on prod
    in an few days
    and I am applying a few enhancements
    Colin Alworth
    i might suggest leaving lombok out of gwt then if it is going out very soon, and stick to what is known to work
    Daniel Korbel
    I use lombok with gwt
    codeserverArgs are my project specific

    Do you haven a stacktrace or project to look at?

    there is some error with latest lombok versions (for my projects)
    see: projectlombok/lombok#2883

    Maybe it is you error too

    Daniel Korbel
    I use one lombok version accross all my modules and it is: 1.18.10
    Colin Alworth
    We're starting an informal gwt contributors/developers call shortly (though i'm running a little late) - please feel free to join us at meet.google.com/kqf-zczm-zis to talk about gwt, j2cl, or the general ecosystem, someone will add you to the room when they're able
    Colin Alworth
    jetty+htmlunit upgrade builds available at https://repo.vertispan.com/gwt-snapshot/com/google/gwt/gwt-dev/2.10.0-htmlunit-upgrade-SNAPSHOT/, add https://repo.vertispan.com/gwt-snapshot/ to your repositories and change gwt version to 2.10.0-htmlunit-upgrade-SNAPSHOT if you want to try it out
    4 replies
    i only just deployed it just now, have done all testing inside of gwt itself so far, just starting to test maven now
    2 replies
    Rocco De Angelis
    Dam that I miss this call. Has this been announced somehow?
    Dmitrii Tikhomirov
    @rdeangelis83 yeah, it was great a meetup. \
    Or Goshen
    hi guys
    in my web.xml file I have a security constraint to force people to use HTTPS
    looks like this:
    when I deploy the war file it all works like peaches
    the problem I have is when I run the server locally using
    mvn jetty:run -pl *-server -am -Denv=dev
    server run normally, but when I try to access it I get
    HTTP ERROR 403 !Secure
    .. naturally since I dont have SSL set on localhost
    what I am forced to do is it comment out the security constant back and forth
    question - is there a way to force the security constant to only aplly to servers other than localhost ?
    Colin Alworth
    @rdeangelis83 we learned to stop publishing the URL ahead of time after we had random people joining when we did that, but we should at least announce the time. The next one will be in three weeks on 30 sept, starting about the timestamp of my last message. it will also be a bit less informal, trying to drum up support for whereever we are with a potential gwt 2.10 release
    Frank Hossfeld
    @niloc132 Mmmh, three weeks should be 07 Oct? Or am I wrong? 😀
    Hi is there any plan to support the latest LTS of java (Java 17) for 2.10?
    Colin Alworth
    @FrankHossfeld you are of course right, the 7th of october
    @MCMicS gwt 2.9 should already run on lts (i think 2.8.2 will too?)
    @MCMicS if you are asking if the new language features will be added, that won't be possible unless we wait quite a while, we need stable support in JDT for this, and they are still at some level of beta eclipse/eclipse.jdt.ls#1845
    and after that, someone will need to take the time to implement the actual features themselves (and to my knowledge, we don't have language features much past java 11 or so? https://docs.oracle.com/en/java/javase/17/language/java-language-changes.html lists language features that were added since java 9 if you want to take a look at where something was added
    text blocks for example should be quite easy to add
    switch expressions will be less easy, but i doubt should be too terrible - but someone will need to take the time to work on it
    Ahmad K. Bawaneh
    As I am checking there isnt many things to be emulated where those you mentioned are good ones ..we also have records, sealed classes, some stream APIs and maybe pattern matching for switch .
    Maybe something like sealed classes is easy as it is infered by the java compiler and the gwt compiler should just ignore it.
    Colin Alworth
    stream apis are "easier" to implement, just have to change our stream emul - language features we have to change the js (or at least adapt how we read the java ast a bit)
    @niloc132 thanks for answering. Yes I mean add new language features and changes to exisiting (like Predicate.not)