Re: SuperDevMode does not see sources from another project (Eclipse)

[david . ostrovsky]

Am Donnerstag, 10. Dezember 2015 11:37:32 UTC+1 schrieb Gordan Krešić:
>
> Suppose I have one library (configured in Eclipse as standalone project - 
> LibProj) and one application (configured in Eclipse as separate project - 
> AppProj) that uses that library.
>
> During regular application development, I include library's .jar with 
> classes and sources and that works flawlessly.
>
> However, while maintaining a library (e.g. adding feature that application 
> uses), I find it useful to add LibProj on AppProj's build path and then 
> hack on both sources without rebuilding library's jar every time. This 
> works for regular Java code, but when I try to invoke SuperDevMode for a 
> module that uses some stuff from library, SDM complains that it can not 
> find sources for used classes. In Eclipse I have no problems 
> compiling AppProj - it sees classes from LibProj, so problem is obviously 
> in sources for that classes.
>
> What I did:
>
> * placed LibProj on AppProj's build path (AppProj -> Properties -> Java 
> Build Path -> Projects)
>
> * made sure that debug configuration that launches SDM has LibProj on 
> classpath (tab Classpath in debug configuration settings)
>
> * made sure that debug configuration that launches SDM has LibProj sources 
> available (tab Sources in debug configuration settings)
>
> What am I missing?
>
>
Add -src ${resource_loc:/LibProj}/src/main/java to gwt_debug
launch configuration. See how related SDM issue was fixed in
Gerrit Code Review: [1].

* [1] https://gerrit-review.googlesource.com/68971

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Jetty 9 before RC1?

[david . ostrovsky]

Am Freitag, 4. Dezember 2015 07:57:12 UTC+1 schrieb Evan Hughes:
>
> Since there are no roadblocks (htmlunit has been updated for jetty 9), is 
> it possible for gwt to update to jetty 9?
>

Yes .

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Update Jetty in GWT?

[david . ostrovsky]

Am Samstag, 30. Mai 2015 02:47:32 UTC+2 schrieb P.G.Taboada:

 Hi,

 I read through some comments, issues and code reviews but I am not sure if 
 an updated Jetty will land in GWT 2.8.

 What is the current status of Jetty update?


Gerrit Code Review, that uses GWT 2.7, was migrated to Jetty 9.x
last year.

To achieve that and to prevent class collisions between Jetty 8
packaged in gwt-dev.jar and Jetty 9 used by Gerrit, outdated Jetty
was stripped from gwt-dev.jar after fetching it from Central: [1].
codeserver must be adjusted: WebServer.java was forked in Gerrit
project: [2].

Jetty upgrade in GWT wasn't possible last year, because of dependency
on HtmlUnit, that was still using Jetty 8 (Websocket). It was fixed recently
and HtmlUnit 2.16 uses Jetty 9 now.

Next steps:

* Upload the dependencies needed for Jetty 9 and HtmlUnit 2.16 upgrade: [3].
* Review the upgrade change: [4].

[1] https://github.com/gerrit-review/gerrit/blob/master/lib/gwt/BUCK#L13,L25
[2] 
https://github.com/gerrit-review/gerrit/blob/master/gerrit-gwtdebug/src/main/java/com/google/gwt/dev/codeserver/WebServer.java#L67,L69
[3] 
https://groups.google.com/d/topic/google-web-toolkit-contributors/ouClai-bTFs/discussion
[4] https://gwt-review.googlesource.com/7857

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Write access to GWT_TOOLS subversion repository

[david . ostrovsky]

What is the policy for write access to GWT_TOOLS subversion repository?

I would like to upload new artifacts needed to verify Jetty 9 and HtmlUnit
2.16 upgrade change [1]. Can someone grant me write access or upload
needed artifacts so that Gerrit verification can succeed?

Thanks.

[1] https://gwt-review.googlesource.com/7857

-- 
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/03d3cda4-40af-4e0e-8c41-b9847ee9344c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Superdev and Jetty 9

[david . ostrovsky]

Am Freitag, 19. Dezember 2014 10:48:05 UTC+1 schrieb david.o...@gmail.com:


 Am Montag, 15. Dezember 2014 14:45:11 UTC+1 schrieb Michael Vogt:

 Hello. 

 Any work going on to solve 
 https://gwt-review.googlesource.com/#/c/7856/  
 https://gwt-review.googlesource.com/#/c/7856/ 


 Unfortunately not. I tried different approaches, but they all failed, 
 because GWT depends on Jetty 8.


I filed this issue for HtmlUnit project as it is the root cause for why GWT 
cannot switch to Jetty 9 atm: [1].

[1] https://sourceforge.net/p/htmlunit/bugs/1656/

-- 
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/3c48aa02-1caa-44d8-b044-19100cbd1933%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Superdev and Jetty 9

[david . ostrovsky]

Am Montag, 15. Dezember 2014 14:45:11 UTC+1 schrieb Michael Vogt:

 Hello. 

 Any work going on to solve 
 https://gwt-review.googlesource.com/#/c/7856/  
 https://gwt-review.googlesource.com/#/c/7856/ 


Unfortunately not. I tried different approaches, but they all failed, 
because GWT depends on Jetty 8.
The most promising approach was to not package Jetty in gwt-dev at all, and 
maintain two different
codeserver versions targeting Jetty 8  Jetty 9. And by not shipping asm 
library in gwt-dev.jar in 2.7
was steps in the same direction. While viable option, this approach was 
abandoned, after codeserver
itself was shipped in gwt-dev.jar.

While all straight forward ways to get GWT + SDM + Jetty9 up and running 
failed, there is a hack:

1. strip outdated Jetty 8 from gwt-dev.jar
2. add dependency to Jetty 9
3. replace one source file from codeserver with this version [1]

See these changes for glory details [2], [3].

[1] 
https://gerrit.googlesource.com/gerrit/+/master/gerrit-gwtdebug/src/main/java/com/google/gwt/dev/codeserver/WebServer.java
[2] https://gerrit-review.googlesource.com/57642
[3] https://gerrit-review.googlesource.com/59354

-- 
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/b6a15c6c-47ef-47dd-b70e-75711c75b633%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.