This would take hours for me to do, and I'm not even sure if I can.. I have to produce a completely new project as I am not at liberty to submit my code from work.
I already located the exact commit which triggered the problem, is there no way you can peek at that to see if there is something obvious? We used to have lots of 'establishing classpath list (scope = compile)' and now we have none. This makes me think that in the haste to remove the multiple identical messages we've stopped establishing compile scope dependency resolution... If we do establish it properly, then we're definitely not passing that classpath to the embedded server. -Jesse On Mon, Nov 1, 2010 at 9:53 AM, Olivier Lamy <[email protected]> wrote: > Hi, > Any way to provide a sample project to reproduce the issue ? > > 2010/11/1 Jesse Farinacci <[email protected]>: >> Hi Oliver, >> >> On Mon, Nov 1, 2010 at 9:47 AM, Olivier Lamy <[email protected]> wrote: >>> Any objections to cut a release 2.1 for the recently released gwt 2.1.0 ? >> >> Yes. There's a huge regression documented in >> http://jira.codehaus.org/browse/MGWT-226 .. if I could mark it as a >> blocker, I would. >> >> -Jesse >> >> -- >> There are 10 types of people in this world, those >> that can read binary and those that can not. >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > > -- > Olivier Lamy > http://twitter.com/olamy > http://www.linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- There are 10 types of people in this world, those that can read binary and those that can not. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
