Hi Riccardo,
I just received my new MBP this week too! I did not do a migration.
Having a clean install of everything has resulted in an Eclipse and
WebObjects setup that works better for me than it ever has in the
past. I think it must have been something that happened during your
migration process that gave you problems.
My only stumble was when I set the development system to use apache
instead of DirectConnect I had difficulty setting the permissions on
the launchdaemon scripts in the wiki. I have been on Tiger before now
so I was using startup items on the previous box. I updated the
procedure for clean Leopard setup in the wiki.
David
On 31-Oct-08, at 10:21 AM, Riccardo De Menna wrote:
I'm replying to myself just in case someone stumbles on the same
thing. I don't know why but the stock MacOs that came with my new
MacBookPro (or maybe the 'migrate from another mac' procedure)
messed up with Java and WebObjects.
Reinstalling the OS and using the 'import users and network
settings' at the end fixed it.
rdm _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/programmingosx
%40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
