Re: [gwt-contrib] GWT 2.8.0-SNAPSHOT

2015-02-02 Thread 'Daniel Kurka' via GWT Contributors
Hi Luca, we are intentionally not deploying right now, but we will eventually sort this out. I am sorry but we do not have an ETA for that. -Daniel On Sun, Feb 1, 2015 at 9:20 PM, luca.masini wrote: > Can someone take the time to fix the problem with the CI system that > prevent the jar to be

Re: [gwt-contrib] GWT 2.8.0-SNAPSHOT

2015-02-02 Thread Jens
> > we are intentionally not deploying right now, but we will eventually sort > this out. I am sorry but we do not have an ETA for that. > Why is it intentionally and why will it only "eventually" be sorted out? Whats going on? -- J. -- You received this message because you are subscribed

Re: [gwt-contrib] GWT 2.8 SnapShot "Unexpected internal compiler error" in SDM after switching to GSS

2015-02-02 Thread 'John Stalcup' via GWT Contributors
If you can provide a small sample that reproduces the problem I will take a look. On Fri Jan 30 2015 at 3:09:32 PM confile wrote: > I use GWT 2.8 SnapShot with an app that runs with CSS only no GSS. Then I > switched to GSS using: > > > > > > "lenient" /> > > > When I compile with option -st

[gwt-contrib] Eclipse project errors

2015-02-02 Thread Jakob Jarosch
Hi, after I've managed to get ANT working I was trying to figure out how to import all those projects into Eclipse. I followed the instructions in trunk/eclipse/README.txt step by step and finally I got a working workspace. But I did some changes to the source where I don't know if I did somethin

[gwt-contrib] Re: Eclipse project errors

2015-02-02 Thread Jens
You should revert all your code changes done in 1-3. All code is intentional and the real problem is the Google Plugin for Eclipse which does not understand JSNI shortcut notation and has some trouble with the UiBinder test files. You can safely ignore these errors. If these errors bug you then

Re: [gwt-contrib] Re: Nextgen GWT/JS Interop (Public) (google-we...@googlegroups.com)

2015-02-02 Thread 'Goktug Gokdogan' via GWT Contributors
@JsExport exports constructors and static members and pins them so they act as entry points and not get pruned. On the other hand, @JsType enforces generation of javascript compatible prototype for the class so if there is a method named "someMethod" in the Java object, same method with same name e

Re: [gwt-contrib] Re: Nextgen GWT/JS Interop (Public) (google-we...@googlegroups.com)

2015-02-02 Thread Joseph Gardi
that makes sense. How would I apply the @JsExport and @JsType to a third party library without forking it though? On Mon, Feb 2, 2015 at 8:11 PM, 'Goktug Gokdogan' via GWT Contributors < google-web-toolkit-contributors@googlegroups.com> wrote: > @JsExport exports constructors and static members a

Re: [gwt-contrib] Re: Nextgen GWT/JS Interop (Public) (google-we...@googlegroups.com)

2015-02-02 Thread 'Goktug Gokdogan' via GWT Contributors
We are going to introduce configuration file based exports in the future however for now your best bet is to super-source the files and add annotations that you need. On Mon, Feb 2, 2015 at 5:21 PM, Joseph Gardi wrote: > that makes sense. How would I apply the @JsExport and @JsType to a third >

Re: [gwt-contrib] Re: Nextgen GWT/JS Interop (Public) (google-we...@googlegroups.com)

2015-02-02 Thread Joseph Gardi
thanks. Sounds exciting. On Mon, Feb 2, 2015 at 8:42 PM, 'Goktug Gokdogan' via GWT Contributors < google-web-toolkit-contributors@googlegroups.com> wrote: > We are going to introduce configuration file based exports in the future > however for now your best bet is to super-source the files and ad

Re: [gwt-contrib] GWT 2.8.0-SNAPSHOT

2015-02-02 Thread Lars
I talked with Daniel at gwt.create about this topic and they have something to fix and won't (or can) talk about this! :-( But he provided a valid workaround for this - you could (very easy) checkout the gwt sources (git) and the (gwt-)tools (svn) and build your own jars. I use targets clean a