It was created 2 years ago
and have to put on prod
in an few days
and I am applying a few enhancements
@italokrenak
<plugin>
<groupId>net.ltgt.gwt.maven</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>${gwt-maven-plugin.version}</version>
<inherited>false</inherited>
<extensions>true</extensions>
<configuration>
<failOnError>true</failOnError>
<sourceLevel>1.8</sourceLevel>
<launcherDir>${project.build.directory}/gwt/launcherDir</launcherDir>
<moduleName>com.app</moduleName>
<moduleShortName>app</moduleShortName>
<jvmArgs>
<arg>
-javaagent:${settings.localRepository}/org/projectlombok/lombok/${lombok.version}/lombok-${lombok.version}.jar=ECJ
</arg>
<arg>-Xms1024m</arg>
<arg>-Xmx4096m</arg>
</jvmArgs>
<codeserverArgs>
<arg>-src</arg>
<arg>${project.parent.basedir}/shared/src/main/java</arg>
</codeserverArgs>
</configuration>
</plugin>
codeserverArgs are my project specific
@italokrenak
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
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
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
in my web.xml file I have a security constraint to force people to use HTTPS
looks like this:
<security-constraint>
<web-resource-collection>
<web-resource-name>Everything</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
<web-resource-collection>
<web-resource-name>Everything</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
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
mvn jetty:run -pl *-server -am -Denv=dev
server run normally, but when I try to access it I get
HTTP ERROR 403 !Secure
HTTP ERROR 403 !Secure
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 ?
@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
@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
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.
I also test it the days to use 17 class files to use within app if source level is still 11
id be happy to try and do the emulated pattern matching libs, but theres a but it would require the shading that my j2cl-maven-plugin does. Its a lot faster and more accurate to write emulated classes and test them in a regular jvm against the real classes being emulated. But something needs to. happen to make this a standard.
Hello folks, I have a strange situation. Iam compiling my gwt-app with gwt-maven-plugin, I have set it up with
gwt-style OBF. The problem is I have an index.html file where I setup / import some external Vue Files with Sysmte.js like follwing: <script>System.import('./js/main.js').catch(function (err) { console.error(err); });</script> in main.js the vue component is implemented and I have also an JsInterop with VueGWT(LINK), where i for example make JsInterops like in main.js I have a method hello: function() { .... } and in my VueComponent.java I have public native void hello();. Overall this works in Detailed Modus when I am compiling the gwt app, but in OBF-Modus it says that the functions are not found . Whats the problem actually ?
i started work to add some new methods and such a while ago, but it hasnt matter enough to many people to have me continue, so i've worked on other things instead
@mP1 weren't not talking about pattern matching libraries, but the language features in the new switch-expression syntax - i dont think runtime language support is needed for that?
@oedemis at a guess, your main.js is calling some gwt function which isnt exported - do you correctly have -generatedJsInteropExports turned on, and is that
hello() method marked as a jsmethod?
Of course there will be runtime support.