Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

['John Stalcup' via GWT Contributors]

change in review at https://gwt-review.googlesource.com/#/c/9850/

On Tue Oct 21 2014 at 3:43:47 PM Stephen Haberman <
stephen.haber...@gmail.com> wrote:

>
> >   if (child.getName().equals(".svn")) // hardcoded filter here
>
> Just curious, but didn't svn change (maybe a year ago or so?) to only
> using one top-level .svn folder, similar to Git's top-level .git
> folder, and not having .svn littered throughout the file system?
>
> - Stephen
>
> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/20141021174343.46a191a4%40sh9.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ-X0ToVXkXW0JivN-VCAYwzzz%3DZKomGnf-%2Bdny7DVGnAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Stephen Haberman]

>   if (child.getName().equals(".svn")) // hardcoded filter here

Just curious, but didn't svn change (maybe a year ago or so?) to only
using one top-level .svn folder, similar to Git's top-level .git
folder, and not having .svn littered throughout the file system?

- Stephen

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/20141021174343.46a191a4%40sh9.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

['John Stalcup' via GWT Contributors]

I think this is a reasonable change to make since it's simple to implement
and a noticeable improvement for SVN users. I'll go ahead and get it in and
we can cherry pick it into this release.

On Tue Oct 21 2014 at 5:58:00 AM Juan Pablo Gardella <
gardellajuanpa...@gmail.com> wrote:

> Thanks for sharing Jérémie. Good to know.
>
> On 21 October 2014 09:32, Jérémie Gottero 
> wrote:
>
>> Do we have an easy way to exclude these folders to see if it improves
>>> things?
>>>
>>
>> Quick and dirty: I overrode the descendToFindResources method to exclude
>> .svn files (note that the file is excluded before isDirectory/isFile calls,
>> avoiding an extra i/o):
>>
>> File[] children = dir.listFiles();
>> for (File child : children) {
>>   if (child.getName().equals(".svn")) // hardcoded filter here
>>   continue;
>>   String childPath = dirPath + child.getName();
>>   if (child.isDirectory()) {
>>
>> Reload time goes down from 2,8s to 1,1sec. The ability to filter files
>> here could lead to interesting speed improvements.
>>
>> Another possible improvement: I got 4874 calls to file.lastModified() in
>> a single browser refresh, for 2088 unique files. Caching the result per run
>> could avoid 50% i/o and reload time would go below 1s. I have no idea if
>> it's realistic/easy to do though, I havent dug in the code ;)
>>
>> --
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/b052327f-8538-4598-b4fb-740cd16d2deb%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFse_4M3ZqrOa2D%2BdQfVhmWvxXABFH7F7y-KkNXKu5HLxcA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ9neWoGRV-ZRwWBSn-8aMo4WnabdK73ooL%2B0o_kXTpuPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0 beta1

['Goktug Gokdogan' via GWT Contributors]

IIRC, there was a bug in compiler where is you call GWT.create on JSO (e.g.
when you inject it via GIN), it will generate a new MyJso call (which
shouldn't work normally as the constructor is protected.)

On Tue, Oct 21, 2014 at 4:06 AM, Jan Thewes  wrote:

> Ok thx. This is what I assumed.
> Will fix this and see how far we can go with 2.7.
>
> Am Dienstag, 21. Oktober 2014 12:51:45 UTC+2 schrieb Daniel Kurka:
>>
>> You can not create a JSO using new in Java. If this has worked with GWT
>> 2.6.1 it is just a bug and should not have worked in the first place.
>>
>> -Daniel
>>
>> On Tue, Oct 21, 2014 at 12:46 PM, Jan Thewes  wrote:
>>
>>> Hello guys,
>>>
>>> we're in the process of trying out GWT 2.7 in our massive application.
>>> Currently we get an error during compile for one module. It worked with
>>> GWT 2.6.1.
>>> Any ideas on this one? I'm not sure but the problem might be that we
>>> can't create a JSO using new ..Jso().
>>> But the big question is why did this work in GWT 2.6.1?
>>>
>>> [ERROR] Errors in 'de/gad/wap/pgu/messenger/ccs/genovoice/event/impl/
>>> JsoEventFactory.java'
>>>
>>>   [ERROR] Line 38: Rebind result 'de.gad.wap.pgu.messenger.ccs.
>>> genovoice.event.call.DialEvent_JsoEvt' cannot be a JSO
>>>
>>>
>>> Cheers,
>>>
>>> Jan
>>>
>>> Am Samstag, 18. Oktober 2014 19:54:40 UTC+2 schrieb Daniel Kurka:
>>>
 Hi all,

 since we are adding major features to GWT, we decided to change our
 release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven
 central and our file storage .
 We are doing this beta to get external feedback on incremental
 compilation and GSS.

 Incremental compilation is now default with GWT 2.7 and replaces,
 together with Super dev mode, the regular old dev mode. Inside of Google we
 are already using it for a while now and most of the issues should have
 already been dealt with, however we also want to make sure that external
 users that might have slightly different use cases will have a working
 2.7.0 release.

 So please start testing with beta1 and give us lots of feedback on the 
 contributor
 list
 
 or on the issue tracker
 . Please
 keep in mind that we did not do any release testing on beta1, so there
 might be issues that you do not expect from a release candidate.

 Our current plan is to wait until the end of next week for any
 feedback. If we do not find any serious external issues we will start the
 testing process for an actual release candidate.

 -Daniel

>>>  --
>>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/google-web-toolkit-contributors/971ba071-e3e7-
>>> 4cfb-978b-ef1fa14853a7%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Google Germany GmbH
>> *Dienerstr. 12*
>> *80331 München*
>>
>> Registergericht und -nummer: Hamburg, HRB 86891
>> Sitz der Gesellschaft: Hamburg
>> Geschäftsführer: Graham Law, Katherine Stephens
>>
>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/a45134df-be98-4ab8-9289-7a52c8248ad7%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA06Dyp_FUMPfYjeutkgFyV9_XSpfqKgRuOFc5Txj3F%3DXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin

[Brandon Donnelson]

Ah, thanks for sharing. I just wanted to double check. By the way if you're 
interested in the GPE preview, I've got that handy if you want to try it 
out. 

On Tuesday, October 21, 2014 10:00:54 AM UTC-7, Matic Petek wrote:
>
> Yes, it was my mistake when I upgrade from 2.6 to 2.7 snapshot. Not it is 
> working. I just want to write it in forum if someone else would have the 
> some problem... Thank you for help.
> Regards,
>Matic
>
> On Tuesday, October 21, 2014 6:41:11 PM UTC+2, Brandon Donnelson wrote:
>>
>> Manolo is correct, the  superdevmode-launcher-legacy.jar is not needed 
>> with GWT 2.7. It can be used with GWT 2.5.x and 2.6.x.
>>
>> Did you add that to the classpath? 
>>
>> Brandon
>>
>>
>> On Tuesday, October 21, 2014 6:03:14 AM UTC-7, Manuel Carrasco Moñino 
>> wrote:
>>>
>>> You shouldn't put never that .jar in your classpath.
>>> GPE takes care of adding it to the launcher classpath when you run 
>>> superdevmode and your gwt is not 2.7. 
>>>
>>> On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek  wrote:
>>>
 I have superdevmode-launcher-legacy.jar in classpath and it is not 
 compatible with GWT 2.7. 
 Regards,
   Matic


 On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote:
>
> I suspect the sdk isn't what you think it is if its not working. Can 
> you check the classpath and see if it was updated? 
>
> On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote:
>>
>> Hi,
>>  I would like to test new compile per file option, but we run our 
>> project from Eclipse and we don't use Maven. So I have perform the 
>> following steps :
>> 1) Download JAR files from https://oss.sonatype.org/
>> content/repositories/google-snapshots/com/google/gwt/
>> gwt-servlet.jar
>> gwt-user.jar
>> gwt-dev.jar
>> gwt-codeserver.jar
>>
>> on 1.9.2014 date
>>
>> 2) Create new "Google" -> "Web Toolkit" configuration
>>
>> 3) select this configuration on my Eclipse project.
>>
>> But when I run hosted mode, I get the error below. Any idea if I'm 
>> doing something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 
>> 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest 
>> version of GWT. Thank you.
>> Regards,
>>Matic
>>
>> Exception in thread "main" java.lang.NoSuchMethodError: 
>> com.google.gwt.dev.javac.CompilationStateBuilder.init(
>> Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V
>>
>> at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)
>>
>> at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)
>>
>> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097)
>>
>> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863)
>>
>> at com.google.gwt.dev.DevMode.main(DevMode.java:379)
>>
>>  -- 
 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 
 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com
  
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/a52b23da-f1ef-4344-b9e8-9ec7f0be9561%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin

[Matic Petek]

Yes, it was my mistake when I upgrade from 2.6 to 2.7 snapshot. Not it is 
working. I just want to write it in forum if someone else would have the 
some problem... Thank you for help.
Regards,
   Matic

On Tuesday, October 21, 2014 6:41:11 PM UTC+2, Brandon Donnelson wrote:
>
> Manolo is correct, the  superdevmode-launcher-legacy.jar is not needed 
> with GWT 2.7. It can be used with GWT 2.5.x and 2.6.x.
>
> Did you add that to the classpath? 
>
> Brandon
>
>
> On Tuesday, October 21, 2014 6:03:14 AM UTC-7, Manuel Carrasco Moñino 
> wrote:
>>
>> You shouldn't put never that .jar in your classpath.
>> GPE takes care of adding it to the launcher classpath when you run 
>> superdevmode and your gwt is not 2.7. 
>>
>> On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek  wrote:
>>
>>> I have superdevmode-launcher-legacy.jar in classpath and it is not 
>>> compatible with GWT 2.7. 
>>> Regards,
>>>   Matic
>>>
>>>
>>> On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote:

 I suspect the sdk isn't what you think it is if its not working. Can 
 you check the classpath and see if it was updated? 

 On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote:
>
> Hi,
>  I would like to test new compile per file option, but we run our 
> project from Eclipse and we don't use Maven. So I have perform the 
> following steps :
> 1) Download JAR files from https://oss.sonatype.org/
> content/repositories/google-snapshots/com/google/gwt/
> gwt-servlet.jar
> gwt-user.jar
> gwt-dev.jar
> gwt-codeserver.jar
>
> on 1.9.2014 date
>
> 2) Create new "Google" -> "Web Toolkit" configuration
>
> 3) select this configuration on my Eclipse project.
>
> But when I run hosted mode, I get the error below. Any idea if I'm 
> doing something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 
> 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest 
> version of GWT. Thank you.
> Regards,
>Matic
>
> Exception in thread "main" java.lang.NoSuchMethodError: 
> com.google.gwt.dev.javac.CompilationStateBuilder.init(
> Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V
>
> at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)
>
> at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)
>
> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097)
>
> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863)
>
> at com.google.gwt.dev.DevMode.main(DevMode.java:379)
>
>  -- 
>>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/9aa8a7c2-24ea-46f9-bcbb-27931d207ded%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin

[Brandon Donnelson]

Manolo is correct, the  superdevmode-launcher-legacy.jar is not needed with 
GWT 2.7. It can be used with GWT 2.5.x and 2.6.x.

Did you add that to the classpath? 

Brandon


On Tuesday, October 21, 2014 6:03:14 AM UTC-7, Manuel Carrasco Moñino wrote:
>
> You shouldn't put never that .jar in your classpath.
> GPE takes care of adding it to the launcher classpath when you run 
> superdevmode and your gwt is not 2.7. 
>
> On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek  > wrote:
>
>> I have superdevmode-launcher-legacy.jar in classpath and it is not 
>> compatible with GWT 2.7. 
>> Regards,
>>   Matic
>>
>>
>> On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote:
>>>
>>> I suspect the sdk isn't what you think it is if its not working. Can you 
>>> check the classpath and see if it was updated? 
>>>
>>> On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote:

 Hi,
  I would like to test new compile per file option, but we run our 
 project from Eclipse and we don't use Maven. So I have perform the 
 following steps :
 1) Download JAR files from https://oss.sonatype.org/
 content/repositories/google-snapshots/com/google/gwt/
 gwt-servlet.jar
 gwt-user.jar
 gwt-dev.jar
 gwt-codeserver.jar

 on 1.9.2014 date

 2) Create new "Google" -> "Web Toolkit" configuration

 3) select this configuration on my Eclipse project.

 But when I run hosted mode, I get the error below. Any idea if I'm 
 doing something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 
 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest 
 version of GWT. Thank you.
 Regards,
Matic

 Exception in thread "main" java.lang.NoSuchMethodError: 
 com.google.gwt.dev.javac.CompilationStateBuilder.init(
 Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V

 at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)

 at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)

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

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

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

  -- 
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/26713a9b-ceb0-47ea-acb8-a2a7492cdbf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Question to Windows users

[Thomas Broyer]

On Tue, Oct 21, 2014 at 4:10 PM, David  wrote:

>
> On Mon, Oct 20, 2014 at 11:47 AM, Thomas Broyer 
> wrote:
>
>>
>> and you need to follow the steps very carefully (and hopefully no
>>> dependency has been changed since the document was written).
>>>
>>
>> I'm curious, which dependencies are you talking about?
>>
>
> In my case it was the checkstyle plugin for eclipse that was not
> compatible with a newer eclipse version. But I gave up shortly afterwards.
>

Ah yes. But nobody forces you to run Checkstyle in the IDE (I don't; when I
tried it some years ago it slowed Eclipse down to being almost unusable).
Maybe we should make things clearer in the doc that it's just a tool and
what matters is that the code is compliant with the style guides, not how
you make sure it's compliant ("ant checkstyle" works too; in my case, I
must confess I don't even run checkstyle on my machine because the rules
are common-sense to me and I rarely violate them – and if I do, then the
checks in Gerrit/Jenkins will slap me in the face)

(note: we since removed our custom checkstyle checks which freed us from
Checkstyle 4.x and have thus been able to upgrade to Checkstyle 5.x)


-- 
Thomas Broyer
/tɔ.ma.bʁwa.je/ 

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEayHEOuz9Wcv9W5noDGOFujCk9fYdcLH1UeTG8L30J_jms_Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Question to Windows users

[David]

On Mon, Oct 20, 2014 at 11:47 AM, Thomas Broyer  wrote:

>
> and you need to follow the steps very carefully (and hopefully no
>> dependency has been changed since the document was written).
>>
>
> I'm curious, which dependencies are you talking about?
>

In my case it was the checkstyle plugin for eclipse that was not compatible
with a newer eclipse version. But I gave up shortly afterwards.


>
>
>>
>> What we do (in an enterprise environment) is to just have a zip or
>> machine image ready to be installed on a new machine. After 30 minutes or
>> so a new developer is ready to code.
>>
>
> In an "Enterprise" environment, you want to "control" the development
> environment so you don't give many choices to the developers.
>

We always have some rogue developers who use vi or IntelliJ, but indeed we
can be very enforcing on what developers have to use. On the other hand,
requiring a VM for development is also a very heavy requirement. I've had
to do such things on a Linux box (with windows in a virtual box) but that
kept on breaking with every update of the linux kernel. But I am not an
Linux expert. I stopped using it a very long time ago (95 or so)


> Here, we want to support different IDEs, we don't want to force you to use
> Eclipse or IntelliJ IDEA or whatever other IDE. Maintaining those ZIPs or
> images is also going to be a hassle I believe.
> I would like to have scripts to help setup the environment, and maybe we
> could have a script that downloads and configure Eclipse for instance (I
> doubt it though); we should have a script to setup the Gerrit commit-msg
> hook without the
>

Well one nice tool (from Google if I am not mistaken) is to use the
workspace mechanic. We use that mostly to keep all our eclipse
installations inline with our rules. Maybe that is an idea to make it
easier.


> need for the contributor to think about it (just run "setup.sh" or
> "setup.bat" and it does the right thing; I fear it wouldn't be that easy on
> Windows though; on Linux, where every tool is an apt-get or yum call away,
> things are much easier, not to mention that distributions come with many
> tools pre-installed: I think every distro comes with Python pre-installed
> because it's needed by other tools already, it might also be the case on OS
> X; but everything seems complicated on Windows, with installers that you
> need to go look for, download, run, answer the questions –i.e. click "next"
> and "OK"– then reboot the machine if you're unlucky; n ow maybe I'm overly
> pessimistic and the needed tools come bundled with "Git for Windows", but I
> know some people won't even install that and instead use the JGit
> integrated within their IDE – and that won't work for us because IIRC JGit
> doesn't run git hooks).
>

I recently had to customize Bootstrap.css to be used in GWT (without GWT
wrappers) and that was really a painful process. It was nearly impossible
to get it working in the enterprise environment. I finally did it on my Mac
at home. But I really hate the fact that nowadays everything seems to be
using their own build systems. Sure ant is crappy and even maven is not
great in many ways ... but boy I was surprised at how many newer things are
available. Always new commands to learn, waste of memory cycles and
confusion when switching between projects.

Anyway, you guys asked for some feedback, there you have it from my point
of view, feel free to do with it what you like :-)

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABrJHW0%2BV8i%3DC2_YK9kwK7bBd36vvziyjVmb2BnGB6nLNNoBxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Official Gradle plugin

[Steffen Schäfer]

Thomas Broyer asked me [1] to post again about this topic to the 
gwt-contrib mailinglist:

That said, I had proposed that there'd be an official gwt-maven-plugin a 
> few years back, and there was no real traction either; and there's almost 
> nobody willing to maintain it (there are people trying the snapshots 
> though, which is great, and they provide feedback).
>
> Too bad that comment didn't happen yesterday, we could have talked about 
> it at the Steering Committee meeting. I'll try not to forget for next 
> month. And yes, post again to the gwt-contrib; your timing last time 
> probably wasn't very good (mid-August, many people are in vacation)
>

I would definitely volunteer to maintain an official Gradle plugin but I 
would be glad if there were 1 or 2 more people willing to help.

I'll wait for an answer at least until next Steering Committee meeting.


[1]: 
https://github.com/steffenschaefer/gwt-gradle-plugin/pull/45#issuecomment-59347003


Am Mittwoch, 13. August 2014 19:20:34 UTC+2 schrieb Steffen Schäfer:
>
> Hi,
>
> Some time ago, I started to create a Gradle plugin for GWT (
> https://github.com/steffenschaefer/gwt-gradle-plugin). Now it’s some kind 
> of popular: in the last weeks the GitHub repo always had >250 unique 
> visitors for a 2 week period (this is what GitHub shows). For me this is a 
> clear signal that a Gradle plugin for GWT is needed.
>
> I personally think it’s time to have a more official solution. I would 
> like to see a plugin in the namespace of org.gwtproject.*. If you agree 
> with this, I would like to contribute my plugin as starting point for an 
> official one.
>
> As I did not accept any external contributions till now, there should be 
> no legal issues.
>
> I planned to write much more but I’m not sure which is the most useful 
> information for you. So I think it’s much better to simply start a 
> discussion about this topic.
>
> If you have any question, don’t hesitate to ask.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/3ad39b96-af29-482c-92b5-795cbf140dad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin

[Manuel Carrasco Moñino]

You shouldn't put never that .jar in your classpath.
GPE takes care of adding it to the launcher classpath when you run
superdevmode and your gwt is not 2.7.

On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek  wrote:

> I have superdevmode-launcher-legacy.jar in classpath and it is not
> compatible with GWT 2.7.
> Regards,
>   Matic
>
>
> On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote:
>>
>> I suspect the sdk isn't what you think it is if its not working. Can you
>> check the classpath and see if it was updated?
>>
>> On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote:
>>>
>>> Hi,
>>>  I would like to test new compile per file option, but we run our
>>> project from Eclipse and we don't use Maven. So I have perform the
>>> following steps :
>>> 1) Download JAR files from https://oss.sonatype.org/
>>> content/repositories/google-snapshots/com/google/gwt/
>>> gwt-servlet.jar
>>> gwt-user.jar
>>> gwt-dev.jar
>>> gwt-codeserver.jar
>>>
>>> on 1.9.2014 date
>>>
>>> 2) Create new "Google" -> "Web Toolkit" configuration
>>>
>>> 3) select this configuration on my Eclipse project.
>>>
>>> But when I run hosted mode, I get the error below. Any idea if I'm doing
>>> something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse
>>> 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest
>>> version of GWT. Thank you.
>>> Regards,
>>>Matic
>>>
>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>> com.google.gwt.dev.javac.CompilationStateBuilder.init(
>>> Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V
>>>
>>> at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)
>>>
>>> at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)
>>>
>>> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097)
>>>
>>> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863)
>>>
>>> at com.google.gwt.dev.DevMode.main(DevMode.java:379)
>>>
>>>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAukR_CEsNP9tL95xSUosBVjjqxgpn7Jis0UznO9PMJWWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Juan Pablo Gardella]

Thanks for sharing Jérémie. Good to know.

On 21 October 2014 09:32, Jérémie Gottero  wrote:

> Do we have an easy way to exclude these folders to see if it improves
>> things?
>>
>
> Quick and dirty: I overrode the descendToFindResources method to exclude
> .svn files (note that the file is excluded before isDirectory/isFile calls,
> avoiding an extra i/o):
>
> File[] children = dir.listFiles();
> for (File child : children) {
>   if (child.getName().equals(".svn")) // hardcoded filter here
>   continue;
>   String childPath = dirPath + child.getName();
>   if (child.isDirectory()) {
>
> Reload time goes down from 2,8s to 1,1sec. The ability to filter files
> here could lead to interesting speed improvements.
>
> Another possible improvement: I got 4874 calls to file.lastModified() in a
> single browser refresh, for 2088 unique files. Caching the result per run
> could avoid 50% i/o and reload time would go below 1s. I have no idea if
> it's realistic/easy to do though, I havent dug in the code ;)
>
> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/b052327f-8538-4598-b4fb-740cd16d2deb%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFse_4M3ZqrOa2D%2BdQfVhmWvxXABFH7F7y-KkNXKu5HLxcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Jérémie Gottero]

>
> Do we have an easy way to exclude these folders to see if it improves 
> things?
>

Quick and dirty: I overrode the descendToFindResources method to exclude 
.svn files (note that the file is excluded before isDirectory/isFile calls, 
avoiding an extra i/o):

File[] children = dir.listFiles();
for (File child : children) {
  if (child.getName().equals(".svn")) // hardcoded filter here
  continue;
  String childPath = dirPath + child.getName();
  if (child.isDirectory()) {
 
Reload time goes down from 2,8s to 1,1sec. The ability to filter files here 
could lead to interesting speed improvements.

Another possible improvement: I got 4874 calls to file.lastModified() in a 
single browser refresh, for 2088 unique files. Caching the result per run 
could avoid 50% i/o and reload time would go below 1s. I have no idea if 
it's realistic/easy to do though, I havent dug in the code ;)

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/b052327f-8538-4598-b4fb-740cd16d2deb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin

[Matic Petek]

I have superdevmode-launcher-legacy.jar in classpath and it is not 
compatible with GWT 2.7. 
Regards,
  Matic

On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote:
>
> I suspect the sdk isn't what you think it is if its not working. Can you 
> check the classpath and see if it was updated? 
>
> On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote:
>>
>> Hi,
>>  I would like to test new compile per file option, but we run our project 
>> from Eclipse and we don't use Maven. So I have perform the following steps :
>> 1) Download JAR files from 
>> https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/
>> gwt-servlet.jar
>> gwt-user.jar
>> gwt-dev.jar
>> gwt-codeserver.jar
>>
>> on 1.9.2014 date
>>
>> 2) Create new "Google" -> "Web Toolkit" configuration
>>
>> 3) select this configuration on my Eclipse project.
>>
>> But when I run hosted mode, I get the error below. Any idea if I'm doing 
>> something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 
>> 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest version 
>> of GWT. Thank you.
>> Regards,
>>Matic
>>
>> Exception in thread "main" java.lang.NoSuchMethodError: 
>> com.google.gwt.dev.javac.CompilationStateBuilder.init(Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V
>>
>> at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)
>>
>> at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)
>>
>> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097)
>>
>> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863)
>>
>> at com.google.gwt.dev.DevMode.main(DevMode.java:379)
>>
>>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] 2.7.0-beta1 deferredjs bypasses application cache

[Richard Wallis]

Thanks Thomas,

 fixes the issue.

It does seem like it might be a browser bug.  It shouldn't be possible to
ever bypass the cache I don't think.

I tried to build a small gwt program to reproduce the error but my small
program worked perfectly.

Still recurs everytime in the app where I found the problem though.

On Mon, Oct 20, 2014 at 10:49 PM, Thomas Broyer  wrote:

> IIRC, Brian changed the behavior of the xsiframe linker to match the
> direct-install linker, because most browsers would otherwise not display
> the source maps. There should be flag to turn it off and go back to the
> previous behavior.
> It however looks like a browser bug worth reporting.
>
> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/b46f94bc-4dc3-45f1-822f-d2df59f7cc8a%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVjDYe9X1s5wjXgqVPGcusHEW-4gZZ-aooCQW9T3tnWESQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0 beta1

[Jan Thewes]

Ok thx. This is what I assumed.
Will fix this and see how far we can go with 2.7.

Am Dienstag, 21. Oktober 2014 12:51:45 UTC+2 schrieb Daniel Kurka:
>
> You can not create a JSO using new in Java. If this has worked with GWT 
> 2.6.1 it is just a bug and should not have worked in the first place.
>
> -Daniel
>
> On Tue, Oct 21, 2014 at 12:46 PM, Jan Thewes  > wrote:
>
>> Hello guys,
>>
>> we're in the process of trying out GWT 2.7 in our massive application.
>> Currently we get an error during compile for one module. It worked with 
>> GWT 2.6.1.
>> Any ideas on this one? I'm not sure but the problem might be that we 
>> can't create a JSO using new ..Jso().
>> But the big question is why did this work in GWT 2.6.1?
>>
>> [ERROR] Errors in 
>> 'de/gad/wap/pgu/messenger/ccs/genovoice/event/impl/JsoEventFactory.java'
>>
>>   [ERROR] Line 38: Rebind result 
>> 'de.gad.wap.pgu.messenger.ccs.genovoice.event.call.DialEvent_JsoEvt' cannot 
>> be a JSO
>>
>>
>> Cheers,
>>
>> Jan
>>
>> Am Samstag, 18. Oktober 2014 19:54:40 UTC+2 schrieb Daniel Kurka:
>>
>>> Hi all,
>>>
>>> since we are adding major features to GWT, we decided to change our 
>>> release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven 
>>> central and our file storage .
>>> We are doing this beta to get external feedback on incremental 
>>> compilation and GSS.
>>>
>>> Incremental compilation is now default with GWT 2.7 and replaces, 
>>> together with Super dev mode, the regular old dev mode. Inside of Google we 
>>> are already using it for a while now and most of the issues should have 
>>> already been dealt with, however we also want to make sure that external 
>>> users that might have slightly different use cases will have a working 
>>> 2.7.0 release.
>>>
>>> So please start testing with beta1 and give us lots of feedback on the 
>>> contributor 
>>> list 
>>>  
>>> or on the issue tracker 
>>> . Please keep 
>>> in mind that we did not do any release testing on beta1, so there might be 
>>> issues that you do not expect from a release candidate.
>>>
>>> Our current plan is to wait until the end of next week for any feedback. 
>>> If we do not find any serious external issues we will start the testing 
>>> process for an actual release candidate.
>>>
>>> -Daniel
>>>
>>  -- 
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Google Germany GmbH
> *Dienerstr. 12*
> *80331 München*
>
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Geschäftsführer: Graham Law, Katherine Stephens
>  

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/a45134df-be98-4ab8-9289-7a52c8248ad7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0 beta1

['Daniel Kurka' via GWT Contributors]

You can not create a JSO using new in Java. If this has worked with GWT
2.6.1 it is just a bug and should not have worked in the first place.

-Daniel

On Tue, Oct 21, 2014 at 12:46 PM, Jan Thewes  wrote:

> Hello guys,
>
> we're in the process of trying out GWT 2.7 in our massive application.
> Currently we get an error during compile for one module. It worked with
> GWT 2.6.1.
> Any ideas on this one? I'm not sure but the problem might be that we can't
> create a JSO using new ..Jso().
> But the big question is why did this work in GWT 2.6.1?
>
> [ERROR] Errors in
> 'de/gad/wap/pgu/messenger/ccs/genovoice/event/impl/JsoEventFactory.java'
>
>   [ERROR] Line 38: Rebind result
> 'de.gad.wap.pgu.messenger.ccs.genovoice.event.call.DialEvent_JsoEvt' cannot
> be a JSO
>
>
> Cheers,
>
> Jan
>
> Am Samstag, 18. Oktober 2014 19:54:40 UTC+2 schrieb Daniel Kurka:
>
>> Hi all,
>>
>> since we are adding major features to GWT, we decided to change our
>> release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven
>> central and our file storage .
>> We are doing this beta to get external feedback on incremental
>> compilation and GSS.
>>
>> Incremental compilation is now default with GWT 2.7 and replaces,
>> together with Super dev mode, the regular old dev mode. Inside of Google we
>> are already using it for a while now and most of the issues should have
>> already been dealt with, however we also want to make sure that external
>> users that might have slightly different use cases will have a working
>> 2.7.0 release.
>>
>> So please start testing with beta1 and give us lots of feedback on the 
>> contributor
>> list
>> 
>> or on the issue tracker
>> . Please keep
>> in mind that we did not do any release testing on beta1, so there might be
>> issues that you do not expect from a release candidate.
>>
>> Our current plan is to wait until the end of next week for any feedback.
>> If we do not find any serious external issues we will start the testing
>> process for an actual release candidate.
>>
>> -Daniel
>>
>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirA57TxELe3AbjSX5Ui%3DzteH%2B2_got4%3DwrywHAYGRxQcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Jens]

>
> These times are incredible slow. The worst I have seen was around 700ms 
> for a huge chunk of code. Normally these times are around ~100ms.
>

Can you define "huge"? Our client side code is about 150 KLOC and with SSD 
a reload takes about 800-1000 ms.

-- J.

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/92bddeaa-0fb6-434e-817e-e23a14dbed08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.7.0 beta1

[Jan Thewes]

Hello guys,

we're in the process of trying out GWT 2.7 in our massive application.
Currently we get an error during compile for one module. It worked with GWT 
2.6.1.
Any ideas on this one? I'm not sure but the problem might be that we can't 
create a JSO using new ..Jso().
But the big question is why did this work in GWT 2.6.1?

[ERROR] Errors in 
'de/gad/wap/pgu/messenger/ccs/genovoice/event/impl/JsoEventFactory.java'

  [ERROR] Line 38: Rebind result 
'de.gad.wap.pgu.messenger.ccs.genovoice.event.call.DialEvent_JsoEvt' cannot 
be a JSO


Cheers,

Jan

Am Samstag, 18. Oktober 2014 19:54:40 UTC+2 schrieb Daniel Kurka:
>
> Hi all,
>
> since we are adding major features to GWT, we decided to change our 
> release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven 
> central and our file storage .
> We are doing this beta to get external feedback on incremental compilation 
> and GSS.
>
> Incremental compilation is now default with GWT 2.7 and replaces, together 
> with Super dev mode, the regular old dev mode. Inside of Google we are 
> already using it for a while now and most of the issues should have already 
> been dealt with, however we also want to make sure that external users that 
> might have slightly different use cases will have a working 2.7.0 release.
>
> So please start testing with beta1 and give us lots of feedback on the 
> contributor 
> list 
>  
> or on the issue tracker 
> . Please keep 
> in mind that we did not do any release testing on beta1, so there might be 
> issues that you do not expect from a release candidate.
>
> Our current plan is to wait until the end of next week for any feedback. 
> If we do not find any serious external issues we will start the testing 
> process for an actual release candidate.
>
> -Daniel
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Jérémie Gottero]

I run the CodeServer on my profiler to see what's going on (see attached 
screenshot). Most time is spent in java.io, meaning that we lost time with 
many disk I/O. Then I looked why I got so much I/O (10k listFiles!), and I 
think it's probably caused by .svn directories. For each directory, 
"descentToFindResources" method enters in 9 folders:

Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn\prop-base
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn\props
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn\text-base
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn\tmp
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn\tmp\prop-base
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn\tmp\props
Descending into dir: 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\client-tmpsrc\com\exalead\.svn\tmp\text-base

Do we have an easy way to exclude these folders to see if it improves 
things?

Jeremie

Le mardi 21 octobre 2014 11:28:28 UTC+2, Daniel Kurka a écrit :
>
> These times are incredible slow. The worst I have seen was around 700ms 
> for a huge chunk of code. Normally these times are around ~100ms.
>
> Something is seriously wrong. Lets try a couple of things:
>
> 1. Up the ram of SDM to see if this makes any difference.
> 2. Are there any other things running on your system that make it slow 
> (lots of other disk IO, other heavy cpu tasks?)
> 3. How much source code are we talking here (LOC, files)?
>
> -Daniel
>
> On Tue, Oct 21, 2014 at 11:23 AM, Jérémie Gottero  > wrote:
>
>> Yes, that was 15sec to detect that nothing has changed. But after some 
>> tries, I actually got better times (~3sec). See logs below, I got 12sec at 
>> first then 3sec. I suspect that my app server load somehow impacts compile 
>> time. Should definitely be a problem on my side.
>>
>> GET /recompile/adminfront
>>Job com.exalead.mercury.admin.ui.AdminFront_1_0
>>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_0
>>   Compiling module com.exalead.mercury.admin.ui.AdminFront
>>  Ignored 22 units with compilation errors in first pass.
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all 
>> errors.
>>  Unification traversed 148143 fields and methods and 10734 types. 
>> 10695 are considered part of the current module and 10695 had all of their 
>> fields and methods traversed.
>>  Compiling 1 permutation
>> Compiling permutation 0...
>> Linking per-type JS with 10679 new types.
>>prelink JS size = 30989214
>>prelink sourcemap = 30989214 bytes and 708768 lines
>>postlink JS size = 30934781
>>postlink sourcemap = 30934781 bytes and 707368 lines
>> Source Maps Enabled
>>  Compile of permutations succeeded
>>  Compilation succeeded -- 43,734s
>>   Linking into 
>> D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\war\adminfront;
>>  
>> Writing extras to 
>> D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\extras\adminfront
>>  Link succeeded
>>  Linking succeeded -- 5,735s
>> *  52,810s total -- Compile completed*
>> GET /recompile/adminfront
>>Job com.exalead.mercury.admin.ui.AdminFront_1_1
>>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_1
>>   skipped compile because no input files have changed
>> *  12,201s total -- Compile completed*
>> GET /recompile/adminfront
>>Job com.exalead.mercury.admin.ui.AdminFront_1_2
>>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_2
>>   skipped compile because no input files have changed
>> *  2,807s total -- Compile completed*
>> [...]
>> GET /recompile/adminfront
>>Job com.exalead.mercury.admin.ui.AdminFront_1_5
>>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_5
>>   Compiling module com.exalead.mercury.admin.ui.AdminFront
>>  Ignored 22 units with compilation errors in first pass.
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all 
>> errors.
>>  Unification traversed 585 fields and methods and 460 types. 9 
>> are considered part of the current module and 9 had all of their fields and 
>> methods traversed.
>>  Compiling 1 permutation
>> Compiling permutation 0...
>> Linking per-type JS with 

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

['Daniel Kurka' via GWT Contributors]

These times are incredible slow. The worst I have seen was around 700ms for
a huge chunk of code. Normally these times are around ~100ms.

Something is seriously wrong. Lets try a couple of things:

1. Up the ram of SDM to see if this makes any difference.
2. Are there any other things running on your system that make it slow
(lots of other disk IO, other heavy cpu tasks?)
3. How much source code are we talking here (LOC, files)?

-Daniel

On Tue, Oct 21, 2014 at 11:23 AM, Jérémie Gottero 
wrote:

> Yes, that was 15sec to detect that nothing has changed. But after some
> tries, I actually got better times (~3sec). See logs below, I got 12sec at
> first then 3sec. I suspect that my app server load somehow impacts compile
> time. Should definitely be a problem on my side.
>
> GET /recompile/adminfront
>Job com.exalead.mercury.admin.ui.AdminFront_1_0
>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_0
>   Compiling module com.exalead.mercury.admin.ui.AdminFront
>  Ignored 22 units with compilation errors in first pass.
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
> errors.
>  Unification traversed 148143 fields and methods and 10734 types.
> 10695 are considered part of the current module and 10695 had all of their
> fields and methods traversed.
>  Compiling 1 permutation
> Compiling permutation 0...
> Linking per-type JS with 10679 new types.
>prelink JS size = 30989214
>prelink sourcemap = 30989214 bytes and 708768 lines
>postlink JS size = 30934781
>postlink sourcemap = 30934781 bytes and 707368 lines
> Source Maps Enabled
>  Compile of permutations succeeded
>  Compilation succeeded -- 43,734s
>   Linking into
> D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\war\adminfront;
> Writing extras to
> D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\extras\adminfront
>  Link succeeded
>  Linking succeeded -- 5,735s
> *  52,810s total -- Compile completed*
> GET /recompile/adminfront
>Job com.exalead.mercury.admin.ui.AdminFront_1_1
>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_1
>   skipped compile because no input files have changed
> *  12,201s total -- Compile completed*
> GET /recompile/adminfront
>Job com.exalead.mercury.admin.ui.AdminFront_1_2
>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_2
>   skipped compile because no input files have changed
> *  2,807s total -- Compile completed*
> [...]
> GET /recompile/adminfront
>Job com.exalead.mercury.admin.ui.AdminFront_1_5
>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_5
>   Compiling module com.exalead.mercury.admin.ui.AdminFront
>  Ignored 22 units with compilation errors in first pass.
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
> errors.
>  Unification traversed 585 fields and methods and 460 types. 9 are
> considered part of the current module and 9 had all of their fields and
> methods traversed.
>  Compiling 1 permutation
> Compiling permutation 0...
> Linking per-type JS with 9 new types.
>prelink JS size = 13769
>prelink sourcemap = 13769 bytes and 338 lines
>postlink JS size = 30934783
>postlink sourcemap = 30934783 bytes and 707368 lines
> Source Maps Enabled
>  Compile of permutations succeeded
>  Compilation succeeded -- 3,147s
>   Linking into
> D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-7\war\adminfront;
> Writing extras to
> D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-7\extras\adminfront
>  Link succeeded
>  Linking succeeded -- 1,753s
> *  8,204s total -- Compile completed*
> GET /recompile/adminfront
>Job com.exalead.mercury.admin.ui.AdminFront_1_6
>   starting job: com.exalead.mercury.admin.ui.AdminFront_1_6
>   skipped compile because no input files have changed
> *  2,782s total -- Compile completed*
>
> Jeremie
>
> Le mardi 21 octobre 2014 10:48:54 UTC+2, Daniel Kurka a écrit :
>>
>> Hi Jeremie,
>>
>> what do you mean by 15s reload? Does the compiler take 15s to detect that
>> you do not have a change? (this would be bad).
>>
>> -Daniel
>>
>> On Tue, Oct 21, 2014 at 10:44 AM, Jérémie Gottero 
>> wrote:
>>
>>> It works like a charm, thanks. I still have ~15sec of "compilation" to
>>> reload the page even when nothing has changed, but I guess it would be
>>> faster with a ssd drive.
>>>
>>>
>>> Le lundi 20 octobre 2014 16:51:19 UTC+2, Daniel Kurka a écrit :

 With GWT 2.7 you do not need any book

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Jérémie Gottero]

Yes, that was 15sec to detect that nothing has changed. But after some 
tries, I actually got better times (~3sec). See logs below, I got 12sec at 
first then 3sec. I suspect that my app server load somehow impacts compile 
time. Should definitely be a problem on my side.

GET /recompile/adminfront
   Job com.exalead.mercury.admin.ui.AdminFront_1_0
  starting job: com.exalead.mercury.admin.ui.AdminFront_1_0
  Compiling module com.exalead.mercury.admin.ui.AdminFront
 Ignored 22 units with compilation errors in first pass.
Compile with -strict or with -logLevel set to TRACE or DEBUG to see all 
errors.
 Unification traversed 148143 fields and methods and 10734 types. 
10695 are considered part of the current module and 10695 had all of their 
fields and methods traversed.
 Compiling 1 permutation
Compiling permutation 0...
Linking per-type JS with 10679 new types.
   prelink JS size = 30989214
   prelink sourcemap = 30989214 bytes and 708768 lines
   postlink JS size = 30934781
   postlink sourcemap = 30934781 bytes and 707368 lines
Source Maps Enabled
 Compile of permutations succeeded
 Compilation succeeded -- 43,734s
  Linking into 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\war\adminfront;
 
Writing extras to 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\extras\adminfront
 Link succeeded
 Linking succeeded -- 5,735s
*  52,810s total -- Compile completed*
GET /recompile/adminfront
   Job com.exalead.mercury.admin.ui.AdminFront_1_1
  starting job: com.exalead.mercury.admin.ui.AdminFront_1_1
  skipped compile because no input files have changed
*  12,201s total -- Compile completed*
GET /recompile/adminfront
   Job com.exalead.mercury.admin.ui.AdminFront_1_2
  starting job: com.exalead.mercury.admin.ui.AdminFront_1_2
  skipped compile because no input files have changed
*  2,807s total -- Compile completed*
[...]
GET /recompile/adminfront
   Job com.exalead.mercury.admin.ui.AdminFront_1_5
  starting job: com.exalead.mercury.admin.ui.AdminFront_1_5
  Compiling module com.exalead.mercury.admin.ui.AdminFront
 Ignored 22 units with compilation errors in first pass.
Compile with -strict or with -logLevel set to TRACE or DEBUG to see all 
errors.
 Unification traversed 585 fields and methods and 460 types. 9 are 
considered part of the current module and 9 had all of their fields and 
methods traversed.
 Compiling 1 permutation
Compiling permutation 0...
Linking per-type JS with 9 new types.
   prelink JS size = 13769
   prelink sourcemap = 13769 bytes and 338 lines
   postlink JS size = 30934783
   postlink sourcemap = 30934783 bytes and 707368 lines
Source Maps Enabled
 Compile of permutations succeeded
 Compilation succeeded -- 3,147s
  Linking into 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-7\war\adminfront;
 
Writing extras to 
D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-7\extras\adminfront
 Link succeeded
 Linking succeeded -- 1,753s
*  8,204s total -- Compile completed*
GET /recompile/adminfront
   Job com.exalead.mercury.admin.ui.AdminFront_1_6
  starting job: com.exalead.mercury.admin.ui.AdminFront_1_6
  skipped compile because no input files have changed
*  2,782s total -- Compile completed*

Jeremie

Le mardi 21 octobre 2014 10:48:54 UTC+2, Daniel Kurka a écrit :
>
> Hi Jeremie,
>
> what do you mean by 15s reload? Does the compiler take 15s to detect that 
> you do not have a change? (this would be bad).
>
> -Daniel
>
> On Tue, Oct 21, 2014 at 10:44 AM, Jérémie Gottero  > wrote:
>
>> It works like a charm, thanks. I still have ~15sec of "compilation" to 
>> reload the page even when nothing has changed, but I guess it would be 
>> faster with a ssd drive.
>>
>>
>> Le lundi 20 octobre 2014 16:51:19 UTC+2, Daniel Kurka a écrit :
>>>
>>> With GWT 2.7 you do not need any bookmarklet stuff anymore. You can just 
>>> bring it up through the old dev mode integration in eclipse, see:
>>>
>>> https://www.youtube.com/watch?v=qpCSbj36O44
>>>
>>> PS: You do not need the -superDevMode anymore its now default.
>>>
>>> On Mon, Oct 20, 2014 at 3:38 PM, Jérémie Gottero  
>>> wrote:
>>>
 Hello,
 I have tried GWT 2.7 beta today, and first of all you guys made an 
 awesome job to reduce compile time (x4/5 faster on my 500k LoC project).
 There is however a CodeServer behavior that I don't understand: why the 
 precompile flag is always turned off in incremental mode?

 if (incremental && !noPrecompile) {

Re: [gwt-contrib] Re: Question to Windows users

[Jonathon Lamon]

Ivy has a specific URL resolver 
(https://ant.apache.org/ivy/history/latest-milestone/resolver/url.html).   
Each URL resolver can have its own pattern and even multiple patterns.  Ivy 
is a very powerful dependency management, way more powerful, imo, than 
maven, but as such it can be confusing.  I setup a custom set of build 
scripts in ant/ivy that we use cross project that basically do everything 
we need to do and allow us to have a common process. You can even make ivy 
deploy maven compatible poms, so that you get both maven and ivy support in 
your dependency repo.  If you wanted to use ivy for publishing or 
retrieving dependencies, I would be glad to help/provide advice.

On Monday, October 20, 2014 6:50:13 AM UTC-7, Jens wrote:
>
> kind of a shame when you're bragging that you can adapt to any situation 
>> and use any kind of dependencies from file() to Maven and Ivy… just not 
>> plain HTTP URLs.
>>
>
> Well Gradle allows you to set a custom repository pattern as it is based 
> on ivy. See section "51.6.9. More about Ivy resolvers" in 
> http://www.gradle.org/docs/current/userguide/dependency_management.html . 
>
> Although the doc does not show it but maybe these patterns can be defined 
> per repository. That way we might be able to use the direct download links 
> of the svn repo at code.google.com.
>
> -- J.
>
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/19c222f5-4439-4a52-aeeb-1eac3df795e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

['Daniel Kurka' via GWT Contributors]

Hi Jeremie,

what do you mean by 15s reload? Does the compiler take 15s to detect that
you do not have a change? (this would be bad).

-Daniel

On Tue, Oct 21, 2014 at 10:44 AM, Jérémie Gottero 
wrote:

> It works like a charm, thanks. I still have ~15sec of "compilation" to
> reload the page even when nothing has changed, but I guess it would be
> faster with a ssd drive.
>
>
> Le lundi 20 octobre 2014 16:51:19 UTC+2, Daniel Kurka a écrit :
>>
>> With GWT 2.7 you do not need any bookmarklet stuff anymore. You can just
>> bring it up through the old dev mode integration in eclipse, see:
>>
>> https://www.youtube.com/watch?v=qpCSbj36O44
>>
>> PS: You do not need the -superDevMode anymore its now default.
>>
>> On Mon, Oct 20, 2014 at 3:38 PM, Jérémie Gottero 
>> wrote:
>>
>>> Hello,
>>> I have tried GWT 2.7 beta today, and first of all you guys made an
>>> awesome job to reduce compile time (x4/5 faster on my 500k LoC project).
>>> There is however a CodeServer behavior that I don't understand: why the
>>> precompile flag is always turned off in incremental mode?
>>>
>>> if (incremental && !noPrecompile) {
>>>   System.out.println("Turning off precompile in incremental mode.");
>>>   noPrecompile = true;
>>> }
>>>
>>> In my dev env, I never use the DevMode On/Off bookmarklets: I always
>>> load js files from the CodeServer url, and I wrote a small GWT utility
>>> class to display a "recompile" button which is embedded in my app UI (it
>>> does the same thing as the bookmarklet, ie calling
>>> codeserverurl/recompile). It's easier to use for others devs: no need to
>>> explain them the bookmarklet stuff, they just have to launch the
>>> CodeServer. With 2.7 I can't use this trick anymore: I need the bookmarklet
>>> to do a first compilation to be able to load my app. Is there a reason to
>>> prevent precompilation in incremental mode?
>>>
>>> Regards,
>>> Jeremie
>>>
>>> --
>>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/google-web-toolkit-contributors/46bc27ce-d8a3-
>>> 40ad-9629-b2c6d3bfe961%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Google Germany GmbH
>> *Dienerstr. 12*
>> *80331 München*
>>
>> Registergericht und -nummer: Hamburg, HRB 86891
>> Sitz der Gesellschaft: Hamburg
>> Geschäftsführer: Graham Law, Katherine Stephens
>>
>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/de430b92-1afd-4843-8b24-83b33ae3179c%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirhXgbCvzMVVptKir204o_fRxYGMdGPu2tdffvkC6Sh%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Jérémie Gottero]

It works like a charm, thanks. I still have ~15sec of "compilation" to 
reload the page even when nothing has changed, but I guess it would be 
faster with a ssd drive.


Le lundi 20 octobre 2014 16:51:19 UTC+2, Daniel Kurka a écrit :
>
> With GWT 2.7 you do not need any bookmarklet stuff anymore. You can just 
> bring it up through the old dev mode integration in eclipse, see:
>
> https://www.youtube.com/watch?v=qpCSbj36O44
>
> PS: You do not need the -superDevMode anymore its now default.
>
> On Mon, Oct 20, 2014 at 3:38 PM, Jérémie Gottero  > wrote:
>
>> Hello,
>> I have tried GWT 2.7 beta today, and first of all you guys made an 
>> awesome job to reduce compile time (x4/5 faster on my 500k LoC project).
>> There is however a CodeServer behavior that I don't understand: why the 
>> precompile flag is always turned off in incremental mode?
>>
>> if (incremental && !noPrecompile) {
>>   System.out.println("Turning off precompile in incremental mode.");
>>   noPrecompile = true;
>> }
>>
>> In my dev env, I never use the DevMode On/Off bookmarklets: I always load 
>> js files from the CodeServer url, and I wrote a small GWT utility class to 
>> display a "recompile" button which is embedded in my app UI (it does the 
>> same thing as the bookmarklet, ie calling codeserverurl/recompile). It's 
>> easier to use for others devs: no need to explain them the bookmarklet 
>> stuff, they just have to launch the CodeServer. With 2.7 I can't use this 
>> trick anymore: I need the bookmarklet to do a first compilation to be able 
>> to load my app. Is there a reason to prevent precompilation in incremental 
>> mode?
>>
>> Regards,
>> Jeremie
>>
>> -- 
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/46bc27ce-d8a3-40ad-9629-b2c6d3bfe961%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Google Germany GmbH
> *Dienerstr. 12*
> *80331 München*
>
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Geschäftsführer: Graham Law, Katherine Stephens
>  

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/de430b92-1afd-4843-8b24-83b33ae3179c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: odd super dev mode times

['John Stalcup' via GWT Contributors]

Ah, thanks for getting to the bottom of it. I agree that we should opt to
use more RAM rather than have randomly slower compiles. And it would be
nice to cherry pick the change into the release branch.

On Mon, Oct 20, 2014, 9:39 PM Stephen Haberman 
wrote:

>
> Well, this is somewhat anti-climatic, but, AFAICT, it was just
> MemoryUnitCache's maps using soft values.
>
> Instead of turning on TRACE everywhere, I upgraded
> MinimalRebuildCache's "known modified type" output to WARN. (It would
> be great to have log4j-style package-level knobs in the GWT log
> output.) That was always right (only 1 .java file with it's 3 inner
> types).
>
> After trying a few other things, I also upgraded
> CompilationStateBuilder's doBuildFrom, where it reads from the unit
> cache, "Used x/y units from cache" line.
>
> And that's it; whenever I have a slow load, I'm loading only ~3k out of
> ~4k units from cache. Or less (I saw zero once, after I had
> particularly annoyed the GC somehow). Whenever it's fast, all ~4k
> (minus the newly invalidated one) are loaded from the unit cache.
>
> I removed MemoryUnitCache's maps' .softValues() and that seems to fix
> it. Upping the Xmx from 1g to 2g also fixes it, and provides a nice
> speed up anyway.
>
> Perhaps 1g was a naively low setting, but, AFAICT, without poking in
> the code (or turning on TRACE and knowing exactly what to look for),
> there are no visible hints about "hey, the cache isn't keeping up,
> that's why your reloads are slow, so up your Xmx".
>
> Given how important the unit cache is now, perhaps the maps should no
> longer use soft values? In my case, I would have preferred an OOME as
> an blatant "needs more RAM" than silent sub-optimal behavior.
>
> - Stephen
>
> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/20141020233903.2a9a93d1%40sh9.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ_tqOMHrG7Jon6521UZquTkQyexbH%3DzerjJmnKmsOequQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.