any other repository I noticed on the gwt.googlesource.com repo.
>
> --
> Colin Alworth
> co...@colinalworth.com
>
>
>
> On Wed, Jun 17, 2020, at 10:29 AM, 'Roberto Lublinerman' via GWT
> Contributors wrote:
>
> The Jenkins server is online, however due to new
The Jenkins server is online, however due to new security related policies
on the compute engine vms run by our teams, we cannot give public access to
the Jenkins instance.
The CI build is running as scheduled. The presubmit is broken, as far as I
can tell it was broken long ago by a Jenkins
ange. Can a googler look into this, or grant us the
> ability to do so?
>
> Thanks,
> Colin
>
> On Monday, July 22, 2019 at 12:48:34 PM UTC-5, Roberto Lublinerman wrote:
>>
>> The issue is still not completely resolved and build.gwtproject.org is
>> still unreacha
The issue is still not completely resolved and build.gwtproject.org is
still unreachable. However continuous builds and presubmits should be
working now.
On Sun, Jul 7, 2019 at 4:39 AM Roberto Lublinerman
wrote:
> I am currently on vacation. The issue is that because of security concerns
&g
I am currently on vacation. The issue is that because of security concerns
new policies are in place regarding use of compute engine by Google teams.
Http and https have been blocked by an enforcer bot. I will sort this out
when I get back. There might be a need to transition out of this
It seems that we are running the build server in a way that a new
enforcement mechanism disables http https serving. I'll follow up on the
issue when I return.
On Sun, Jun 30, 2019 at 1:30 PM Roberto Lublinerman
wrote:
> fixed
>
> On Sun, Jun 30, 2019 at 1:20 PM Roberto Lublinerman
It seems that there was some automatic configuration change that added a
few firewall rules. I am looking into this but I will be out for a couple
of weeks and I don't know if I'll be able to fix that before I return.
On Sat, Jun 29, 2019 at 12:42 PM Jens wrote:
> Can anybody with the
To save you some pain, you should probably use the WSL (Windows Subsystem
for Linux). You can track the progress for and contribute to making it work
natively in https://github.com/google/j2cl/issues/9.
On Wed, Nov 21, 2018 at 4:32 PM Jason Washo wrote:
> Awesome! I'm starting the process now.
Looking at this traces it seems to me that the file/line is consistent but
the member is completely off. That suggests that the wrong symbol map is
being used.
On Mon, Jul 30, 2018 at 4:40 AM Jens wrote:
> In production we sometimes get exceptions and we log them using
> StackTraceDeobfuscator
You can also set it up from the gradle build script here:
https://gwt-review.googlesource.com/c/gwt/+/7984. It is quite outdated but
I think with minimal work it might be brought up to date. I have used it in
the past with success.
On Wed, Apr 25, 2018 at 1:28 AM Jens
On Mon, Apr 9, 2018 at 11:19 PM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:
> I'm stuck with a few issues in JDT compiler those make not possible to
> launch "super sourced" tests at source level >= 9.
> So, I have to first make patches for JDT and create custom JDT build
> before
On Thu, Apr 5, 2018 at 10:59 PM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:
> Ok. I'll prepare and upload the patch.
>
> Thanks for pointing out the solution's direction.
>
Np. Thanks for contributing to the compiler proper :).
I was giving another look at the code and the safest
On Thu, Apr 5, 2018 at 2:07 AM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:
>
> Yes, all i had to do to make non-denotable type to work, is to replace
> `$Local$` type with anonymous synthetic class name `Outer$1` when creating
> JClassType for JLocal.
>
>
Ok. So you changed
On Wed, Apr 4, 2018 at 12:36 AM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:
But for non-denotable types GWT compiler breaks with assertion. E.g. it
> breaks for anonymous local class:
> var tuple = new Object(){ int first, second; };
>
> It's because type binding for this declaration
Anybody up for reviewing https://gwt-review.googlesource.com/c/gwt/+/20580?
--
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
> There are also Java9 depeding issue which will not be reviewed for example.
>>
>
> Yeah I agree, Java9 support, including new API emulations, should find its
> way into GWT sooner than later. GWT usually has to wait for a good Eclipse
> JDT release as GWT uses it to parse and compile GWT
I would wait until an eclipse jdt release is done and upgrade JDT.
On Tue, Sep 26, 2017 at 10:56 AM, Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:
> JDT has a bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=521438) that
> make it super slow to compile some project involving
The correct link for the patches are
https://gwt-review.googlesource.com/#/c/19000/
https://gwt-review.googlesource.com/#/c/19020/
On Wed, Jul 26, 2017 at 6:29 PM, Roberto Lublinerman <rlu...@google.com>
wrote:
> I have uploaded two patches for review to allow GWT to run under a Ja
I have uploaded two patches for review to allow GWT to run under a Java 9
vm.
https://gwt-review.googlesource.com/#/c/19000/
https://gwt-review.googlesource.com/#/c/19001/
The main issue is (as noted by James) that the class loading has been
revamped and GWT can no longer assume that the class
n for all the answers so far.
>
> Vassilis
>
> On Tue, Jun 27, 2017 at 7:40 PM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> You can call it a missing feature. Clearly not a bug, not everything that
&g
You can call it a missing feature. Clearly not a bug, not everything that
can be done in JS is available from Java with interop. For these situations
you probably want to have some JS stubs.
On Tue, Jun 27, 2017 at 1:09 AM, Vassilis Virvilis
wrote:
> Ok guys this is the last
>
>
> @Roberto
> Please note that I am not mixing stuff (java and js objects in the same
> array, or different kind of objects in the same array).
>
> D3 is doing the correct thing here. If you pass an array of something,
> let's say T[] you can expect that you will be getting T and T[] out of D3
ail.
>
> --
> Colin Alworth
> co...@colinalworth.com
>
>
>
> On Mon, Jun 26, 2017, at 12:09 PM, 'Roberto Lublinerman' via GWT
> Contributors wrote:
>
> The short answer is that this is also not a bug.
>
> Java arrays are typed, JS arrays are not.
The short answer is that this is also not a bug.
Java arrays are typed, JS arrays are not. So none of the examples you have
will fully work.
E.g. If you do array instanceof Date[] on an array built in JS filled with
Dates it will fail.
A native array is best modeled as SomeNativeJsType[] where
The declaration
package somepackage;
@JsNative(isTrue, name = "ordinal")
class Ordinal {
}
effectively says that there is a native type "somepackage.ordinal", which
d3.ordinal is not.
You can model it as a native interface for example where there is not such
expectation.
So as
We relaxed restriction checking to allow void return type from getters.
Cl is up for review:
https://gwt-review.googlesource.com/#/c/18020/
On Thu, Apr 6, 2017 at 3:17 PM, Jens wrote:
> Hmm, I have just built gwt head from source and used the above jars but
> SDM
You probably have a misconfigured class path. The symptoms are consistent
with trying to compile rc3 GWT SDK emulation library with an rc2 compiler.
On Thu, Oct 13, 2016 at 10:05 AM, Teletin Alin
wrote:
> Forgot to say that with:
>>
> The pom.xml versions for gwt:
>
The error suggests a class path issue. The same patch that introduced
in native string relaxed the checking for namespaces in the
compiler to allow this situation (
https://gwt-review.googlesource.com/#/c/16881/).
On Wed, Sep 21, 2016 at 2:46 AM, stuckagain wrote:
> It
Arnaud, have you tried using -strict? GWT ignores compilation units with
errors if they are not explicitly reachable from the entry point. I assume
your Toto class is only referenced from JS. So if this class has any
compile error (like missing references) then GWT does not see the class,
much
${gwtversion}
>
>
>
>
>
> com.google.gwt
>
> gwt-servlet
>
> ${gwtversion}
>
>
>
>
>
>
>
>
>
>
>
> -Xms1024M -Xmx8g -Xss1024k
>
>
>
>
>
> compile
>
>
>
>
>
>
>
>
You might need to increase the heap size. JDT still uses more memory under
Java 8 which is the source level that is currently supported by GWT (try
-Xmx3g or -Xmx4g).
On Thu, Aug 4, 2016 at 11:27 AM, Mark Duesbury
wrote:
> Hi .. Thanks for the rc...
>
> I have been
Looking at the elemental code that uses a lambda which will not be
EventHandler but a JsFunction. Could you try with an anonymous EventHandler
instead?
On Tue, Aug 2, 2016 at 1:51 AM, Steve Andrews
wrote:
> I've created a quick test project and put it at
>
I filed a bug with a minimal repro at
https://github.com/gwtproject/gwt/issues/9379 and uploaded a fix for review
at https://gwt-review.googlesource.com/#/c/15450
On Wed, Jul 20, 2016 at 11:23 AM, Roberto Lublinerman <rlu...@google.com>
wrote:
> Could you guys file an issue for thi
The error messages were introduced by mistake in the JSNI error reporting
fix (https://gwt-review.googlesource.com/#/c/15080) and the fix for those
is up for review https://gwt-review.googlesource.com/#/c/15120/
On Thursday, June 9, 2016 at 8:55:36 AM UTC-7, Hristo Stoyanov wrote:
>
> Thomas,
You could use Impl.getNameOf() (look
at gwt/user/test/com/google/gwt/junit/client/GWTTestCaseStackTraceTest.java
for an example of usage). Note that using this feature will disable some
optimizations on the target function.
That being said, this is an internal functionality and could
bar(x); }
>
> bar(Object x) { if (x instanceof Callable) { print("it's a callable");
> } else if (x instanceof Runnable) { print("It's a runnable"); } }
>
> You need a castMap for that.
>
>
> On Mon, Apr 18, 2016 at 10:17 AM, 'Roberto Lublinerman' via GWT
sn't
> inline.
>
> You want something like x -> 42 + capture to compile to
> makeLambda(function(x) { return 42 + capture }, castMap, classLit),
> not function(x) { return Class.foo(capture, x); } do you not?
>
>
> On Mon, Apr 18, 2016 at 9:49 AM, 'Roberto Lubl
; removes the unused inner class.
>
> I think if you try to model this in the Java AST it would impact too much
> stuff.
>
>
> On Mon, Apr 18, 2016 at 9:04 AM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
> > We accep
a's, especially for JsFunction. When 2.8
> gets released, I think people will really start taking advantage of
> existing JS libraries that really heavily use functions.
>
>
> On Friday, April 15, 2016 at 12:03:12 PM UTC-4, Roberto Lublinerman wrote:
>>
>> It should not be
:57:00 AM UTC-4, Roberto Lublinerman wrote:
>>
>> Yes, right now all lambdas are implemented as anonymous inner classes,
>> even the ones implementing JsFunction interfaces.
>>
>> On Fri, Apr 15, 2016 at 6:11 AM, Paul Stockley <pstoc...@gmail.com>
>> wrot
Yes, right now all lambdas are implemented as anonymous inner classes, even
the ones implementing JsFunction interfaces.
On Fri, Apr 15, 2016 at 6:11 AM, Paul Stockley wrote:
> Am I right in saying that java 8 lambda's under the covers is implemented
> as an anonymous
I am not sure what should be included. I use our internal setup that has
all those targets configured correctly already. In the open source build I
normally build the distributions and then inlcude gwt-dev.jar and
gwt-user.jar, IIRC.
On Wed, Apr 6, 2016 at 2:24 PM, Michael Zhou
curred while
> executing this line:
> E:\gwt-2.8.0-beta1\samples\DynaTable\build.xml:40: Java returned: 1
>
> Total time: 11 seconds
>
> Am Mittwoch, 11. November 2015 08:30:53 UTC+1 schrieb Roberto Lublinerman:
>>
>> It happens in windows with or without the flag I th
No plan to support through Java implementors, although there are plans to
support varargs which would let you accomplish something similar.
On Nov 10, 2015 08:53, "Manuel Carrasco Moñino" wrote:
> I see, it works, thanks.
>
> Any plan to work as well with gwt exported classes
PM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:
> Also is this happening in any other configuration? Java8? windows 10?
>
> I can't reproduce it with mac or linux.
>
>
> On Tue, Nov 10, 2015 at 9:39 PM, 'Robe
Could you run it with -Dgwt.watchFileChanges=false and let us know? That
flag should turn of the file watching logic.
On Tue, Nov 10, 2015 at 6:39 AM, Lars wrote:
> After the "Redo file watching refactor." change
> (d746d952defbd42c81317ccbd5da0f1561b81d36) both
>
> I did not use pretty style because I thought that this flag produces
> different result, I tested now and looks like the output is the same, but,
> I'm pretty sure that some flags changes this issues, optimize is obvious
> that fixes the problem, but I think that namespace=package also changes
It would be really helpful if you could isolate your problem to a small
example.
On Mon, Oct 26, 2015 at 2:39 PM, Roberto Lublinerman <rlu...@google.com>
wrote:
> I did not use pretty style because I thought that this flag produces
>> different result, I tested now and looks
Use Bug-link, see https://gwt-review.googlesource.com/#/c/13710/
On Sun, Oct 25, 2015 at 5:25 AM, Jens wrote:
> Hi,
>
> In Gerrit "Bug: issue " points to Google Code. Do we already have an
> alternative wording for cross linking to Github? Something like "Bug:
>
Are you using a recent snapshot?
On Oct 24, 2015 04:40, "Ignacio Baca Moreno-Torres"
wrote:
> There is a bug which optimizations nullify variables which might not be
> null. I'm trying to reproduce the error outside our app but I can't, I'll
> continue trying, but for now I
3f9d8c7b07 (6 October 2015
>> at 04:29:19 GMT+2), I'll try tomorrow with HEAD, but looking the commits
>> looks improbable that the problem has been solved.
>>
>> On Sat, Oct 24, 2015 at 10:30 PM 'Roberto Lublinerman' via GWT
>> Contributors <google-web-toolkit-contribut
'Roberto Lublinerman' via GWT
Contributors google-web-toolkit-contributors@googlegroups.com wrote:
This might be due to the way we handle class literals. Class literals
for interfaces if not referenced during the initial compile might cause
that error. The error should go aways if you restart SDM
.
Chris
On Mon, Jun 8, 2015 at 6:55 PM 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
This might be due to the way we handle class literals. Class literals
for interfaces if not referenced during the initial compile might cause
that error
are most likely to
use SDM in uncompiled mode, and the 'error' can always be suppressed and
turned into a warning. At best, it might inhibit a const optimization in
Closure where it sees the same variable declared/assigned twice I think.
On Tue, Jun 9, 2015 at 10:27 AM, 'Roberto Lublinerman
This might be due to the way we handle class literals. Class literals for
interfaces if not referenced during the initial compile might cause that
error. The error should go aways if you restart SDM.
The offending sequence is
0) Suppose initially you have (interface A, class B and class C) and
Balázs, the js.embedded.properties configuration property might help here.
Try adding
extend-configuration-property name=js.embedded.properties
value=my.platform /
to your gwt.xml file
On Tue, May 5, 2015 at 6:26 AM, Kishore Palakollu
kishorepalako...@gmail.com wrote:
Hi Robert,
Lambdas work fine in master.
On Fri, Apr 24, 2015 at 6:02 PM, Stephen Haberman
stephen.haber...@gmail.com wrote:
Just curious, but what is the state of lambdas on master?
Probably works? Known broken in some hairy boundary cases? Being
used in production?
Thanks,
Stephen
--
You
Please file an issue to keep track.
On Mon, Mar 30, 2015 at 9:06 AM, Roberto Lublinerman rlu...@google.com
wrote:
GWT strings and arrays are JS native strings and arrays (no prototype
monkey patching), in Java code calls to Object, String, Array and
Comparable methods are devirtualized
GWT strings and arrays are JS native strings and arrays (no prototype
monkey patching), in Java code calls to Object, String, Array and
Comparable methods are devirtualized if applied to instances typed at one
of those types.
So the answer is yes: You wont be able to call instance methods this
failed) ?
On Thu, Mar 19, 2015 at 5:45 PM 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
We are looking into it and will be hopefully resolved soon.
On Thu, Mar 19, 2015 at 8:15 AM, Colin Alworth niloc...@gmail.com
wrote:
It looks like
I think we make run presubmits with Java 8. AFAIK presubmit only build the
compiler (to see that is buildable) and run checkstyle. We will still run
our main continuous build in Java 7 and there is an alternate continuous
build with Java 8 (which is now broken).
Can someone look at those
We are looking into it and will be hopefully resolved soon.
On Thu, Mar 19, 2015 at 8:15 AM, Colin Alworth niloc...@gmail.com wrote:
It looks like the build is failing, and has been for some days:
http://build.gwtproject.org/job/gwt/49/#showFailuresLink
Test Result (26 failures / -6)
Can you provide a small repro case and open an issue for it?
On Wed, Mar 18, 2015 at 6:15 AM, Travis Schmidt travis.schm...@gmail.com
wrote:
I hit a similar problem. I Turned on GSS with GWT 2.7 Release. I
converted one of my files to .gss and let the converter handle the other
files for
In draft compile Java compile time constants are emitted in the prototype.
This should be exactly static final fields of primitive or string type
assigned at declaration.
This is the approach to compile time constants taken to implement Java
semantics.
FWIW in optimized compiles other fields
wrote:
Static final fields on the prototype? I'm pretty sure these are
promoted to global in optimized mode. Perhaps you meant final
non-static fields? (which we should have an optimization for promoting
to static :) )
On Fri, Dec 5, 2014 at 7:29 AM, 'Roberto Lublinerman' via GWT
This looks awfully a class path issue. Did you ant clean before building?
On Fri, Nov 14, 2014 at 3:06 AM, Julien Dramaix julien.dram...@gmail.com
wrote:
I've updated my master branch (of the GWT-core project) the with the
remote and now I'm not able to run any GWT test cases included in the
The reason why your are seeing error (1) in 2.7 and not in 2.6 (I assume)
is that to implement minimal (class level) recompiles all the methods of a
class are traversed in 2.7 where only entry point reachable methods were
traversed in 2.6. In the past if you had a class that, for example,
There seems that some assertions in UnifyAST are not being satisfied in
incremental SDM but it runs fine (and correctly) if you turn off assertions.
On Wed, Oct 29, 2014 at 10:53 PM, jay j...@thegindins.com wrote:
I grabbed the RC and switched to use it from my IntelliJ project.
When starting
Yes. Will be fixed before final release.
On Thu, Oct 30, 2014 at 2:23 PM, jay j...@thegindins.com wrote:
I'll give that a try...
Will the issue be handled before the final release?
jay
On Thursday, October 30, 2014 11:47:54 AM UTC-7, Roberto Lublinerman wrote:
There seems that some
John detected that behavior in the persistent unit cache and has a fix for
it.
On Oct 19, 2014 7:16 PM, Stephen Haberman stephen.haber...@gmail.com
wrote:
...and, right now, I can't even get the 3s time to kick in again.
Ah ha...seems to be something with the PersistentUnitCache.
When the
The time it takes to compile depends not only on how many files are
modified but also how big is the invalidation caused by the modification.
Depending what gets invalidated it might require running more generators or
(re) compiling many more types.
Also the first few compiles are also warming up
Can you isolate the bug and open an issue for it? If you upload a repro
case I'll take a look.
On Fri, Oct 3, 2014 at 11:52 AM, Stephen Haberman
stephen.haber...@gmail.com wrote:
Hey,
I know FF17 is pretty old, but do we care about breakages in it? We
noticed some client-side
Can you reproduce that from the command line in a regular compile? If so
can you post all the flags passed to the compiler?
On Wed, Oct 1, 2014 at 2:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:
Am I the only one to have this problem ?
On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix
This seems to be the error:
java.lang.IncompatibleClassChangeError: class
com.google.gwt.dev.javac.asm.CollectMethodData has interface
org.objectweb.asm.MethodVisitor as super class
and the problem seems to be that you have ASM 5 in your class path. (It
seems that MethodVisitor was an interface
I'll look into it.
Manolo,
Do you know what is the Building Unknown Task that is showing in our
jenkins instance?
On Wed, Oct 1, 2014 at 2:49 PM, Manuel Carrasco Moñino man...@apache.org
wrote:
Roberto, in my case this is the command line:
Fixed. Review at https://gwt-review.googlesource.com/#/c/9432.
The issue is only present with -localWorkers 1 and all workers except the
first would get incorrect options.
On Wed, Oct 1, 2014 at 4:23 PM, Roberto Lublinerman rlu...@google.com
wrote:
I'll look into it.
Manolo,
Do you know
So out of pure curiosity - are there obvious optimizations in the linker
which are still pending?
We have been thinking about strategies to incrementalize the work done by
the linkers, one idea is to have a linker that outputs js for different
Java classes to different resources and that
We upgraded to checkstyle 5.7 in trunk (
https://gwt-review.googlesource.com/#/c/6670/). If you checkout out trunk
or download the nighty builds (2.7.0-SNAPSHOP) from maven all the required
changes (to ant, the style files, etc) are there.
On Sat, Jun 7, 2014 at 1:26 AM, Michael Prentice
The problem with implementing clone() at object is that it is an breaking
change because of the rules for JSOs. JSOs are required to implement (and
declare final) all Object methods because there is no dynamic dispatch. So
having clone() at Object implies either implementing it in JavaScriptObject
Those maven snapshots were done while testing. The logs for the failed
builds are not showing maven uploads.
On Wed, Apr 30, 2014 at 3:45 AM, Jens jens.nehlme...@gmail.com wrote:
Thats cool, however it seems like that builds with failing tests are
pushed out to Maven? Jenkins build #27 and
AFAIK I see no reason why symbolMaps are incompatible with
collapse-all-properties.
SymbolMaps seem to be controlled by compiler.useSymbolMap property and are
emitted by SymbolMapsLinker.
Perhaps on one of the permutations that property is set to false? Line 261
in SymbolMapsLinker.java seems to
It is now a know problem. In fact from 2.5 to 2.6 there have been small
improvements in compilation speed (on large projects).
W.r.t. the exception in obfuscated mode, did you observe the problem on one
permutation or in multiple?
On Wed, Apr 2, 2014 at 9:52 PM, Michael Vogt
Sorry for the mistype. I meant it is NOT a known problem. If you can
provide an example that reproduces that behaviour I would love to debug it.
On Thu, Apr 3, 2014 at 9:35 AM, Roberto Lublinerman rlu...@google.comwrote:
It is now a know problem. In fact from 2.5 to 2.6 there have been small
A type error like might just be equivalent to a java NullPointerException.
Once the application is compiled to JavaScript instead of producing NPEs it
produces TypeErrors. If you run it with -style PRETTY it might give you a
hint where in the code the type error is ocurring and you might be able
It would be interesting to look at the Symbol map corresponding to the
breaking permutation and see what are the functions Bf and Xeb.
On Thu, Apr 3, 2014 at 10:11 PM, Michael Vogt i...@michaelvogt.eu wrote:
Just verified: When compiling the same code with style detailed, there
is no
I don't know whether it is only me or a general problem but in my local
repo Gerrit seems to be acting up, pushes take forever and end up in error.
On Tue, Feb 18, 2014 at 8:24 PM, Roberto Lublinerman rlu...@google.comwrote:
Roberto Lublinerman has uploaded a new patch set (#2).
Change
api-checker is in!
On Wed, Feb 12, 2014 at 6:07 PM, Goktug Gokdogan gok...@google.com wrote:
I have plenty of patches that were waiting for apichecker. Can you hold of
until next week?
On Wed, Feb 12, 2014 at 12:35 PM, John Stalcup stal...@google.com wrote:
I'm going to do a one time
:40 AM UTC-8, Roberto Lublinerman wrote:
The bug in the post is not due to the issue being discussed in the
thread. If you can attach a small project that repros the bug you are
getting, I'll take a look.
Best,
Roberto.
On Wed, Jan 22, 2014 at 10:30 PM, jay jay.g...@gmail.com wrote:
I
The bug in the post is not due to the issue being discussed in the thread.
If you can attach a small project that repros the bug you are getting, I'll
take a look.
Best,
Roberto.
On Wed, Jan 22, 2014 at 10:30 PM, jay jay.gin...@gmail.com wrote:
I realize that about the only thing in common is
Some changes to sourcemap generation require a version newer than 20131014.
The sourcemap part of the closure tools can probably be compiled with as
Java 6.
On Fri, Jan 17, 2014 at 9:12 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Friday, January 17, 2014 3:59:58 PM UTC+1, Artur Signell
Yep, I have just checked and sourcemap-rebased.jar is version 51.0 (i.e.
compiled with Java7). GWT takes this dependency from the public closure
release.
On Thu, Jan 9, 2014 at 3:13 PM, Jens jens.nehlme...@gmail.com wrote:
Looks like IE6 hasn't been completely removed?
Oh that reminds me
It seems that the build script needs to pass -sourceLevel 6 when compiling
.gwtars (which we seem to ship incompiled form). I think I saw a patch or
email regarding that issue.
On Mon, Dec 9, 2013 at 8:17 AM, Matthew Dempsky mdemp...@google.com wrote:
Hm, so is building with Java 6 a new
Hi Colin,
Did you do ant clean? I find it strange that the resource points to
Matthew's hard drive, as if Impl was precompiled by him (and in that case
probably is consistent that the version is 51.0).
I build from scratch in my laptop (only has java 1.6) and builds and tests
run fine. Is there
AM UTC-6, Roberto Lublinerman wrote:
Hi Colin,
Did you do ant clean? I find it strange that the resource points to
Matthew's hard drive, as if Impl was precompiled by him (and in that case
probably is consistent that the version is 51.0).
I build from scratch in my laptop (only has java 1.6
On Wed, Nov 13, 2013 at 9:33 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Wednesday, November 13, 2013 5:41:12 PM UTC+1, Cristiano wrote:
Hi All,
I then think that it is needed a patch to include guava-15.0-rebased.jar,
sourcemap-rebased.jar, protobuf-java-rebased-2.5.0.jar and
UTC-6, Roberto Lublinerman wrote:
You should be able to invoke devmode with -sourceLevel 6.
Roberto Lublinerman | Software Engineer | rlu...@google.com javascript:
| 408-500-9148
On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth nilo...@gmail.comjavascript:
wrote:
I'm not yet convinced
You should be able to invoke devmode with -sourceLevel 6.
Roberto Lublinerman | Software Engineer | rlu...@google.com | 408-500-9148
On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth niloc...@gmail.com wrote:
I'm not yet convinced that this isn't either a) a workspace issue or b) a
decision
Fantastic.
On Sun, Oct 20, 2013 at 9:28 PM, Stephen Haberman
step...@exigencecorp.comwrote:
Wow, that sounds awesome, Matthew. Great work. I'm looking forward to
hopefully *not* triggering this great feedback. :-)
- Stephen
--
On Sun, Oct 20, 2013 at 3:21 PM, Thomas Broyer t.bro...@gmail.com wrote:
See $GWT_TOOLS/lib/eclipse/README.jdt-upgrade (last paragraph), and
comments in https://gwt-review.googlesource.com/#/c/2361/1/dev/build.xml (if
you understand them; reading them now, I don't ;-) )
In retrospective I am
Seems to point that JavaScriptObject.class was compiled in java 7 mode but
the codeserver is running in a java 6 vm.
On Wednesday, October 16, 2013 2:19:54 PM UTC-7, Cristiano wrote:
Hi All
maybe I can be a little off-topic posting here but this is not an usual
user question and hopefully
1 - 100 of 317 matches
Mail list logo