--
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-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com.
We kind of knew this sort of incompatibility would happen, but I still
think GWT should continue get out of the business of rebasing
everything.
We should even have a version of the JAR that can use
dynamic dependencies.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7fUFGt8ksPPoPTwhxUN2xBjVLLoJ%2B%3DbooMpDoy6cN5wWg%40mail.gmail.com.
On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors <google-web-toolkit-contri...@googlegroups.com> wrote:We kind of knew this sort of incompatibility would happen, but I still
think GWT should continue get out of the business of rebasing
everything.We should even have a version of the JAR that can use
dynamic dependencies.I think this is a good option. Can we go with it?
--
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-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/7b0c9a48-094a-4782-a362-52828a9505ee%40googlegroups.com.