So, to be pedantic:
Language features -> no issues there at all, since JDT happily compiles
java 8 code w/ a java 9-compatible compiler.
Emul updates -> standard "don't use java 9 methods if you need java 8
support"
Classpathery -> Made it use ugly reflection to not require java 9 classes
on
We use single permutation (safari) for all browsers, if you do not, you
have to look at
target\projectName-1.0-SNAPSHOT\projectName\compilation-mappings.txt
in order to understand which script is current.
Then go to
target\projectName-1.0-SNAPSHOT\WEB-INF\deploy\projectName\symbolMaps
just look in to the directory and look into the files. damn easy
i don't remember exactly (can build my project and write later)
среда, 7 июня 2017 г., 23:54:42 UTC+3 пользователь rjcarr написал:
>
> > There is a file (produces during build) with all names mapping to java
> methods. You can
> There is a file (produces during build) with all names mapping to java
methods. You can de-obfuscate it manually.
This sounds like exactly what I need. Not to take more of your time, but
do you have any references where I can get more information about this?
Thanks!
--
You received this
Hi
They're getting an unresponsive script error, and the browser will tell
> them where it is, but the code is obfuscated.
>
It is not an issue if you have obfuscated stack trace. There is a file
(produces during build) with all names mapping to java methods. You can
de-obfuscate it manually.
>
> Are there specific Java9 JRE classes that we should focus on to get into
> GWT?
>
>
I didn't go through the full changelog, but I believe there have been more
helper methods added to Optional and other classes; will need emul updates
for sure.
> Would making GWT support Java9 sources
Are there specific Java9 JRE classes that we should focus on to get into
GWT?
Would making GWT support Java9 sources and running in a Java9 env cause
backward incompatible changes that prevent GWT from running in Java8?
On Wednesday, June 7, 2017 at 2:56:46 PM UTC-5, James Nelson wrote:
>
> As
Thanks for the response, and yes, totally inaccessible by any means.
So back to my main question: are there any serious ramifications, mostly
related to runtime (as I understand the issues with loading), with running
a non-obfuscated application?
Thanks!
--
You received this message because
If your production site is not remotely accessible then there is nothing
you can do. You have to go there.
If the site is accessible from your browser (even with ssh tunnels) the
technique I suggested is employable.
Vassilis
On Wed, Jun 7, 2017 at 11:13 PM, Robert J. Carr
thanks for the clarification.
Maybe a sufficiently strong wording in the compatibility guarantees is
enough.
Something like this: We will try really hard to not rename all methods and
move all packages around in the next week commits. However we may introduce
incompatible changes as we are
Hi Vassillis-
Thanks for the response. A few comments:
> the problem is reproducible in the remote system and not just happens
after several hours of usage
It's not entirely reproducible, but does seem to happen with some
regularity. And yes, it has hours of usage, which could be the problem.
Also, the reason gwt.xml files aren't loading sanely has to do with how
resources are handled in java 9.
You are going to have to either declare your source modules (with the
gwt.xml) as `open` (no documentation for this, I found it trolling JCP
forums),
or you can open your module to your
Here is an idea assuming
a) the problem is reproducible in the remote system and not just happens
after several hours of usage
b) it is a client side error and not a server side error
You can try to use bookmarklets for compilation in super dev mode. There
are some hurdles to overcome,
As I've mentioned
elsewhere, https://plus.google.com/+JamesNelsonX/posts/gBfpBDnwV9V , java 9
support is entirely possible.
When I last tried it out, it required a fair number of hacks, but it worked
fine.
I expect the final version of java 9 modules to require slightly fewer
hacks,
and for
Hi.
Per this thread:
https://plus.google.com/+JamesNelsonX/posts/gBfpBDnwV9V
I have actually dove into Java 9 support, and cleared all the roadblocks
once (before the JCP pushback force the module system to get more last
minute changes).
The main issue was not language support (easy upgrade
I've been using GWT for years and years but recently my customers have a
problem that I can't reproduce, and they're remote so I can't just go check
it out in person.
They're getting an unresponsive script error, and the browser will tell
them where it is, but the code is obfuscated.
I'm
There is some reasoning behind us not broadly announcing elemental2 and the
jsinteorp generator:
They are both still beta software in the sense that we know there are
existing problems, but we already want feedback on them.
There are still no guarantees on APIs / compat but if you are brave and
Ah yes that explains it. It was j2cl that I remembered.
Thanks for the clarification.
Vassilis
On Wed, Jun 7, 2017 at 9:40 PM, Colin Alworth wrote:
> I think you may be misremembering - the jars were released to maven as
> experimental last summer, then as beta in
I think you may be misremembering - the jars were released to maven as
experimental last summer, then as beta in April, and only after that were
they on github.
J2CL is not expected to be dropped until it is "ready", but as with
elemental2, this isn't going to mean "bugfree" but more like
Looks like they are also here in source form
https://github.com/google/elemental2
https://github.com/google/jsinterop-generator
I thought google didn't want to release them before they were "ready". So
either they changed their mind, or they feel it is ready or I don't
remember correctly :-)
The groupId has changed - using the mvnrepository site, try
https://mvnrepository.com/artifact/com.google.elemental2 to see all of the
jars now available.
On Wednesday, June 7, 2017 at 11:14:33 AM UTC-5, Bruno Salmon wrote:
>
>
>
>> Additionally, this supports the recent beta release of
>
> Additionally, this supports the recent beta release of jsinterop.base and
> elemental2, available from Maven Central.
>
>
>
Where can we find that elemental2 beta release (I can see only the June
2016 version on that page
See https://groups.google.com/forum/#!topic/google-web-toolkit/5KrtRLw6gYo for
usage of gwt 2.8.x with java6
On Wed, 7 Jun 2017 at 12:10 Daniel Kln wrote:
> Hello everyone,
>
> i want to traverse a file system like in following example:
>
> function traverse(entry,
Hello everyone,
i want to traverse a file system like in following example:
function traverse(entry, path) {
path = path || "";
if (entry.isFile) {
// Get file
item.file(function(file) {
console.log("File:", path + file.name);
});
} else if (entry.isDirectory) {
Hello,
Any idea about plan to support GWT for java 9 which is to be released by
july end.
thanks.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Did you find any solution to this. I am facing same issue
I tried to pass vm arg --add-modules=java.se.ee but still it doesnot work.
On Wednesday, February 15, 2017 at 2:47:30 PM UTC+5:30, Dave Bradlee wrote:
>
> At Labkey.com we're trying to compile all of our code, which includes GWT
> code,
26 matches
Mail list logo