I am seeing the same thing. Curious if this really is a jvm bug, how is this working at google?
On Thursday, July 19, 2012 11:20:30 AM UTC-4, JoseM wrote: > > I put in a bug report: > http://code.google.com/p/google-web-toolkit/issues/detail?id=7536 > > On Thursday, July 19, 2012 6:38:28 AM UTC-4, Thomas Broyer wrote: >> >> >> >> On Thursday, July 19, 2012 6:44:04 AM UTC+2, JoseM wrote: >>> >>> If it helps I am trying to build this using my Mac. >>> >>> I also realized that there is also now a 2.5-rc1 version of the plugin >>> so I tried with that one and I still get the deadlock: >>> >> >> It's not surprising, as the deadlock is in GWT, not the gwt-maven-plugin. >> >> As a workaround, try using <localWorkers>1</localWorkers> (or >> -Dgwt.localWorkers=1) to use a single-threaded build and hopefully avoid >> the deadlock. >> >> You'll note also that it seems to rather be a bug in Java rather than in >> GWT, as the locks seem to have been created by standard classes (java.awt.* >> and sun.security.*) rather than GWT ones. >> >> Worth a bug report for GWT though (and then see how it's triaged) >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Qro43-VMcwMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
