On Thursday, October 2, 2014 2:33:29 PM UTC+2, Manuel Carrasco Moñino wrote: > > > > On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors < > [email protected]> 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? >
I'm currently updating the scripts that push JARs to Maven to unbundle ASM, along with the POMs to add the dependency on ASM. I'll also add dependencyManagement to com.google.gwt:gwt and com.google.web.bindery:requestfactory (aka make them "bills of material") so you could use them with <scope>import</scope> in your dependencyManagement to make sure you use everything with the same version, even when some deps are transitive (e.g. you use a lib that depends on gwt-dev with a version different than the one you use for gwt-user; dependencyManagement helps solve these issues). Other deps we could easily replace with non-rebased ones are Guava and Protobuf. -- 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 [email protected]. 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. For more options, visit https://groups.google.com/d/optout.
