Hey Jim,
Based on your comments in the bug report, it looks like the fact that your
app uses Swing is what causes the problem. In that case,
-XstartOnFirstThread should not be present. Unfortunately, due to the way
that the Web Application Launch Configurations work, there is no way to
disable
That's what I was thinking too. Not a problem, and I really
appreciate your testing and followup on this. It's no problem for me
to continue to start devmode from the command line for now.
On Dec 21, 7:51 am, Rajeev Dayal rda...@google.com wrote:
Hey Jim,
Based on your comments in the bug
FWIW, I get the same behavior. I did a quick fix by editing
the .launch and build.xml files so that .XstartOnFirstThread were
suppressed. OTOH, I'm kinda freaked out by this; would like assurance
that this is really a bug in the toolkit and that -XstartOnFirstThread
is really supposed to work.
Which files did you edit?
On Dec 17, 11:59 am, Madprof kickingve...@gmail.com wrote:
FWIW, I get the same behavior. I did a quick fix by editing
the .launch and build.xml files so that .XstartOnFirstThread were
suppressed. OTOH, I'm kinda freaked out by this; would like assurance
that this
Hi Jim,
A couple of questions:
-What version of Java 6 is installed on your machine (do a java -version to
find out)? Do you experience the same problem with a different version of
Java 6 (not sure if Apple allows you to have multiple minor JDK versions on
your system at the same time), or with
Hi Jim,
I was unable to reproduce this issue. I was using the following platform:
Mac OS X 10.5.8
Java 1.6.0_17
Eclipse - Java Edition, 64 bit, Cocoa (running with Java 1.6.0_17)
Now, here's the thing: -XstartOnFirstThread IS added the command-line, but
that is intentional; we did that so that
Jim,
One other question - are you using Eclipse's Development Mode View, or did
you set the USE_REMOTE_UI environment variable in your launch configuration
to disable it? If you did, I think I can see why you're running into
problems. We've got a bug in the plugin where we're not removing
-XstartOnFirstThread IS added the command-line, but that is intentional
Ahh, that's useful information! Would it be possible to make that a
configurable option?
I just generated the trivial Web Application Starter Project, and it
runs without generating those error messages. But I'm not sure
GWT 2.0 seems to be working ok here, but I've been noticing floods of
these error messages in the console:
2009-12-16 12:17:55.552 java[25151:13b03] *** -[NSConditionLock
unlock]: lock (NSConditionLock: 0x143e511a0 '(null)') unlocked when
not locked
2009-12-16 12:17:55.553 java[25151:13b03] ***
Hmm. Ok, I think I have a vague idea what's happening, but I don't
know why. When I start my GWT Web App from Eclipse, the command line
includes -XstartOnFirstThread. If I copy that entire command line and
run it from a command shell -- but omit -XstartOnFirstThread -- then
those errors go
10 matches
Mail list logo
