I'm pretty sure it's not necessary to do a reboot (it's Java, what do
we care :) ) ... I suspect you may still be able to get that
condition to occur on a new project. I don't run into anything like
that with existing projects, just with new ones. When I get some
time, that one is high up on my list, because it totally screws new
users of eclipse, which are the "most vulnerable".
ms
On Aug 15, 2006, at 10:33 AM, Kieran Kelleher wrote:
> Hi Mike,
>
> I wiped all, reinstalled from scratch. Followed instructions to the
> letter. I created and deleted WOLipsTest 5 times and no good. Then
> I decided to just reboot my machine and launch Eclipse to try
> again ........ this time the new WOApplication worked! So, instead
> of an Eclipse restart after installing all the updates, perhaps a
> full reboot is necessary. I dunno. My machine spec is:
> MacBook Pro 2GB RAM 2.13GHz OS X 10.4.6 i686-C.Duo / Java
> 1.4.2_09 / WO 5.3.1 & P. Wonder / XCode v2.2.1 / MySQL 4.1.18-
> std / Connector-J 3.0.17
>
> Perhaps add a note to Step 18 of the install tutorial "A full
> machine reboot is recommended."
>
> Does the fact that I have the eclipse folder in my home folder make
> a difference at:
> ~/Applications/eclipse/Eclipse.app ?
>
> OK, so I proceeded through your tutorials ........... works great!
>
> First impressons of Eclipse (coming from everyday use of
> XCode) ............
> better code completion :-)
> automatic package import statements :-)
> building in the background :-)
> hot code replace :-) very cool.
>
> Thanks!
>
> Regards, Kieran
>
> On Aug 15, 2006, at 7:45 AM, Mike Schrag wrote:
>
>>> Issue #1 (may or may not be contributing to the problem)
>>> On http://www.objectstyle.org/confluence/display/WOL/Install
>>> +WOLips+with+Eclipse+Update+Manager, step 12 :
>>> When I click Select Required, I get less items selected than
>>> Mike shows in the picture. I just assumed that Mike selected some
>>> extras when doing the screenshots that are not required by WOLips.
>> Eclipse bug ... They switched to a lazy-loading tree at some point
>> in the 3.2 timeframe. As a result, if you haven't expanded the
>> Callisto tree node, they don't find other required plugins. Try
>> just opening the top tree node, THEN select required. This broke
>> sometime after I wrote the docs and I haven't had a chance to
>> update them.
>>
>>> Issue #2 (probably contributing to my trouble)
>>> When I create the WOLipsTest project at
>>> http://www.objectstyle.org/confluence/display/WOL/Create+a+new+WO
>>> +Application, step 6,7
>>> I have a different set of objects than shown in the pic....
>>> - I have a 'bin', but no 'build'
>>> - I have no WO Frameworks (must this be connected manually?)
>>> - I have no JRE System Library (must this be connected manually?)
>> Problem #2 and #3 are related to this. There is a race condition
>> somewhere inside of the project creation wizard. I tried to track
>> it down when I was at WWDC, but I couldn't find it at the time.
>> I'm on "real work" for about two weeks before I can get back to
>> this, but maybe Ulrich will have some time to take a look at this
>> one. What happens is that under certain conditions, New
>> WOApplication project wizard ends up NOT becoming a WOLips or Java
>> project, and as a result, you don't end up with a build folder or
>> WOFrameworks. If you delete the project and try to create one
>> again, it might fix it. This is REALLY bad for new people because
>> there's just no explanation as to what happened. What kind of
>> machine do you have? This seems to be more repeatable on slower
>> machines, though it DOES happen on my MBP as well (just not as
>> often).
>>
>> ms
>
This archive was generated by hypermail 2.0.0 : Tue Aug 15 2006 - 11:03:49 EDT