OOPHM and Mac OSX

[P.G.Taboada]

Hi,

it's working on my Mac Snow Leopard as long as I don't start the shell
from Eclipse. I have seen some posts about doing this and that but it
looks like they are all out of date.

Any help/ tips here for the current trunk?

brgds,

Papick

[Jason Parekh]

Hi Papick,

Where does it exactly break when you start from Eclipse?  Do you have any logs?  (One place to check is WORKSPACE/.metadata/.log)

thanks
jason

[P.G.Taboada]

Hi,

in the meantime I tried the milestone one, but I have the same issue.
The Swing window opens but is frozen. The cursor is the funny coloured
sprinning "wait" ball.

In the console I get:

2009-10-13 12:18:41.881 java[11686:903] [Java CocoaComponent
compatibility mode]: Enabled
2009-10-13 12:18:41.883 java[11686:903] [Java CocoaComponent
compatibility mode]: Setting timeout for SWT to 0.100000
2009-10-13 12:18:43.106 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x1001a17c0> '(null)') unlocked when
not locked
2009-10-13 12:18:43.108 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:43.226 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x12dba4b70> '(null)') unlocked when
not locked
2009-10-13 12:18:43.227 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:43.328 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x12db23ec0> '(null)') unlocked when
not locked
2009-10-13 12:18:43.328 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:43.436 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x100141b60> '(null)') unlocked when
not locked
2009-10-13 12:18:43.441 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:43.548 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x12db04120> '(null)') unlocked when
not locked
2009-10-13 12:18:43.548 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:43.751 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x100133ce0> '(null)') unlocked when
not locked
2009-10-13 12:18:43.752 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:43.882 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x1001aa470> '(null)') unlocked when
not locked
2009-10-13 12:18:43.883 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:43.995 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x1001aae70> '(null)') unlocked when
not locked
2009-10-13 12:18:43.995 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:44.154 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x12dbac5c0> '(null)') unlocked when
not locked
2009-10-13 12:18:44.155 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:44.306 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x12db9ebc0> '(null)') unlocked when
not locked
2009-10-13 12:18:44.307 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:44.419 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x12dbace60> '(null)') unlocked when
not locked
2009-10-13 12:18:44.425 java[11686:db03] *** Break on _NSLockError()
to debug.
2009-10-13 12:18:44.534 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x1001ab8a0> '(null)') unlocked when
not locked
2009-10-13 12:18:44.534 java[11686:db03] *** Break on _NSLockError()
to debug.
Using a browser with the GWT Development Plugin, please browse to
the following URL:
http://localhost:8080/MyApp.html?gwt.hosted=192.168.15.206:9997
2009-10-13 12:18:44.985 java[11686:db03] *** -[NSConditionLock
unlock]: lock (<NSConditionLock: 0x1001ad120> '(null)') unlocked when
not locked
2009-10-13 12:18:44.986 java[11686:db03] *** Break on _NSLockError()
to debug.


Any help?
Anyone got this working from a Mac?

brgds,

Papick

On 21 Sep., 17:48, Jason Parekh <jasonpar...@gmail.com> wrote:
> Hi Papick,
>
> Where does it exactly break when you start from Eclipse?  Do you have any
> logs?  (One place to check is WORKSPACE/.metadata/.log)
>
> thanks
> jason
>

[Miguel Méndez]

I think that this is issue 3923.  We should have a plugin update by end of day today.  

--
Miguel

[P.G.Taboada]

That sounds really good. Thx.

On 13 Okt., 12:44, Miguel Méndez <mmen...@google.com> wrote:
> I think that this is issue

> 3923<http://code.google.com/p/google-web-toolkit/issues/detail?id=3923>.

>  We should have a plugin update by end of day today.
>

[willr3]

I am experiencing the same problem when trying to launch OOPHM from
within Eclipse and I have OSX 10.6. I did notice that even though the
swing UI hangs I am still able to manually direct the browser to the
correct URL and interact with my GWT project however it is very slow.
Do you know if the plugin update was already delivered?

[Miguel Méndez]

The plugin update was pushed out last night.  You plugin's notification system should kickoff within the next 24hrs.  You can always manually trigger a check for updates from eclipse.

--
Miguel

[Will]

I updated my eclipse plugins and still see the spinning beach ball
when I place the focus on the Swing UI. I am running on OSX 10.6 and
am using FF 3.5 with the latest plugin and a new build of GWT from
trunk. The console output is similar to what P.G. posted. Any
guidance on where to look / what to try to hopefully resolve this
issue?

--Will

[Miguel Méndez]

Can you post back the command line from the problematic launch configuration? (You can see what the command line is by right-clicking on the process in the Debug View and selecting properties)  Also, are you using a Contributor SDK?

--
Miguel

[Will]

I managed to resolve the spinning beach ball by restarting eclipse
after I regenerated GWT from trunk. My only guess is that the old
libraries were still being held in memory and were not being replaced
by the new ones? I'm at a loss but at this point I'm no longer
getting the beach ball. Thank you to everyone who worked on resolving
this problem.

[ma]

Hello,

I had exactly the some problems as you described them.
In my case the solution was a jvm argument "-XstartOnFirstThread"
which was necessary on macs. Without the argument it works well.

Regards,
Markus Albrecht