Re: All In One Installer broken
Re: All In One Installer broken
- Subject: Re: All In One Installer broken
- From: Tim Worman <email@hidden>
- Date: Sun, 6 Dec 2009 10:51:15 -0800
Also, I'm not a shell scripting maestro but I'd volunteer effort to help keep a tool installer updated.
Tim Worman
UCLA GSE&IS
On Dec 6, 2009, at 9:36 AM, Kieran Kelleher wrote:
> I was setting up a new SL dev environment, and just to see what the initial installation and setup procedure would be like for a complete newbie on SL, I looked on the wiki for instructions for the simplest possible path to new installation on a virgin Snow Leopard.
>
> It seems that really, a newbie would probably be confused and would probably struggle. :-(
>
>
> After installing WebObjects 5.4.3 using Apple's dmg installer and then installing the "All In One" Eclipse/WOLips installer from Jeremy's .mac page (since the sisu download was slow as molasses with an est time of 1 day+!), I then hit a roadblock, getting an error when launching Eclipse after running Jeremy's installer.
> " An Error has occurred"
> " See the log file ~/.eclipse/...../blahblah.log"
>
> That error log file is full of "missing required bundle" messages.
>
> Anyway, just FYI, I don't have time for troubleshooting this now .... I am doing my usual 3.4.2 download and install/setup the manual way.
>
> Since Jeremy is not working in WO anymore and this is AIO (All In One) installer is clearly broken for install on a virgin OS X Snow Leopard box, we might want to just discontinue the all-in-one installer and just go write a concise "WebObjects Developer Quick Start Guide" for newbies .......so I started a wiki page on this and will work on completing it as I get time. Any thoughts on that? Should I wipe all references on the wiki to the AIO?
>
> If we are ever going to get new devs to come to WebObjects, we need to have a working quick start. Any dev worth his salt should be comfortable on the command line, so maybe a bash install script that downloads and installs various bits and configures everything might be the better route. Any opinions on that?
>
> BTW, I went to use the WOInstaller.jar initially and thinking that a newbie would want standard install paths, I set the WOInstaller.jar target as "/", but got an error saying System directory already exists. Should the WOInstaller.jar's CPIO class be changed to just overwrite existing files? Does that "overlay" directory paths (aka merge eith existing files if named differently, or does it realyl "replace" existing directories (ie., wiping them out)?
>
> Anyway, this is just some meandering thoughts / discussion before I leave off the "How would a newbie WO dev fare on getting started" for now and go do some work.
>
> Regards, Kieran
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden