In the mean time though, I think I successfully pushed 2.6.0-SNAPSHOT to
https://oss.sonatype.org/content/repositories/google-snapshots/.
On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky mdemp...@google.comwrote:
As promised, I created the release/2.6 branch for tracking development
towards
Thanks Mathew!
2013/11/5 Matthew Dempsky mdemp...@google.com
In the mean time though, I think I successfully pushed 2.6.0-SNAPSHOT to
https://oss.sonatype.org/content/repositories/google-snapshots/.
On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky mdemp...@google.comwrote:
As promised, I
Hi Stephan,
Could you please let me know is there any patch available to check the
impact of removing de rpc calls.
Thanks in advance..
Have a good day.
Regards,
Naresh Yakkala.
On Thursday, 20 September 2012 20:18:39 UTC+5:30, Stephen Haberman wrote:
Or should I go ahead and propose a
Never used it because I didn't like the API. It hides the async behavior
completely which makes it easy to fall into traps. IMHO its just too much
hiding.
Once GWT supports Java 8 and once GWT provides additional API methods that
play nicely together with lambda/method references there is no
Hi Naresh,
Could you please let me know is there any patch available to check
the impact of removing de rpc calls.
I'm glad you're interested in looking in to this.
Unfortunately, I don't really know much about DeRPC. There are probably
others on the gwt-contrib list who do though...we'll see
Never used it
Same here, so +1 to your plans to extract it.
- Stephen
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving
The first step would be to delete com.google.gwt.rpc and the
HybridServiceServlet, and then remove all the hooks in RPC that were added
to make deRPC possible (there's at least one in RemoteServiceServlet), and
probably others in the RPC generator.
On Tuesday, November 5, 2013 5:26:21 PM
Just curious, is there a particular impetus to removing DeRPC at this time?
E.g., is it causing code bloat or slowness, or making new development more
difficult?
I'm fine with marking the class as @Deprecated, but unfortunately we
[Google] still have an internal customer using DeRPC and so far I
DeRPC was essentially an experiment that didn't work out, it was supposed
to improve the speed of IE6. It added a lot of hacks to the compiler to
make it work, @ArtificialRescue, ability to invoke client-side methods from
server emitted functions, which actually requires clever hacks in some
It looks like while I can get maven from the command line to get along with
that repo, IntelliJ isn't having it - it is getting confused by the fact
that the latest gwt-user snapshot 2.6.0-20131105.081128-3 only has a
sources jar and a pom, no actual jar with compiled code in it. The -1 jar
is
Sorry, let me clarify: I know what DeRPC is and why we'd want to get rid of
it. I'm asking why we're discussing getting rid of it *now*.
Like I said, Google has an internal user for it still, so someone (most
likely me) would need to invest time in helping them transition off before
we can
Thanks for testing, Colin! I'll try another push tonight using your
scripts.
On Tue, Nov 5, 2013 at 5:14 PM, Colin Alworth niloc...@gmail.com wrote:
It looks like while I can get maven from the command line to get along
with that repo, IntelliJ isn't having it - it is getting confused by the
12 matches
Mail list logo
