Re: All In One Installer broken
Re: All In One Installer broken
- Subject: Re: All In One Installer broken
- From: Jeremy Matthews <email@hidden>
- Date: Mon, 07 Dec 2009 16:48:18 -0500
Just here to help...if that works for the group, great.
If you guys need to move in a different direction, I completely understand.
Thanks,
jeremy
On Dec 6, 2009, at 5:36 PM, Joe Little wrote:
> Let me apologize for the group, and hope you stay with us a little longer. We all tend to use the mailing list as the official conduit of communications and forget that direct email may be preferred when reporting a problem for some. Worse yet, bringing up such issues over a weekend can be a recipe for more disastrous fun. The only bit I agree on is making it even more obvious to new users whatever the group preffered methods are. Anything to limit confusion is _usually_ best.
>
> On Dec 6, 2009, at 12:20 PM, Jeremy Matthews <email@hidden> wrote:
>
>> Clearly broken, eh?
>> I suppose after seeing more than a dozen messages no one thought of actually talking to me?
>> Sigh...so many assumptions, so little meaningful conversation....
>>
>> I'm not sure what the issue is, since we test it routinely, and this is the first time we've heard in MONTHS that there was a problem. And now there's talk of abandoning it entirely - within an hour.
>> Nice.
>>
>> So, seems everyone wants to talk AROUND me and not TO me, let me make a few things clear:
>> 1) I regularly test and maintain the installer.
>> 2) Whenever we hear there is an issue we FIX it. Usually pretty damn fast. Ask around.
>> 3) I do not build WO Apps _ROUTINTELY_ anymore - this does not mean I care less about the tools or the installer, or the great people in the community. I still develop too, I just don't advertise it. Usually the opposite since there are tons of talented people here.
>>
>> That being said, if someone wants to take the installer over, fine by me. I've had fun working with some really cool people, and being able to create something a lot of people thanked me for.
>>
>> I've been fortunate to work with this great community, and am sincerely thankful for that. But...if people will not communicate with me, then there is nothing I can do (to help this community). I wish everyone the absolute best of luck.
>>
>> So long, and thanks for all the fish!
>>
>> -jeremy
>>
>> P.S. - There have a been more than a few people along the way who said they owed me a beer. If I see you at WWDC, I'll be collecting those!
>>
>>
>> #####
>> 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