Hi Try this Installer
http://www.ksroom.com/App/WebObjects/Kisa.woa/wa/woDeploy I have already Installed 9 Machines with it and it is done in a few Minutes. Ken On 2012/07/25, at 4:51, Jeffrey Schmitz wrote: > On a similar subject, I'm trying to setup a new Lion server machine for > deployment. I'm trying to use these instructions: > > http://wiki.wocommunity.org/display/documentation/Deploying+on+Mac+OS+X+Server > > But I'm not getting very far because (I think) of changes made to Lion. > > The first thing that's unclear to me is what steps need to be done. Are the > first two Install WeObjects... sections an either or proposition, or do you > have to do both, or something in between? I'm thinking the part about > installing mod_WebObjects.so in the second section needs to be done > regardless which method you use to install webobjects. > > Continuing, after installing using the Apple installer, when I try to install > the mdimension mod_WebObjects.so file, the directory referenced as containing > the old module (/System/Library/WebObjects/Adaptors/Apache2.2) doesn't exist. > So my main question is, where do I need to install the mod_WebObjects > module on Lion, and where is the old one installed? > > Thanks, > Jeff > > On Jul 21, 2012, at 1:42 PM, Pascal Robert wrote: > >> >> Le 2012-07-17 à 21:30, G Brown a écrit : >> >>> What do you all think? >>> >>> ...Oh, let me explain.... >>> >>> There is documentation for WOLips scattered in the Wonder wiki, the WOLips >>> wiki, (WebObjects wiki?) etc. >>> >>> Why? Would it be a good idea to have it in one place/wiki? And then refer >>> with those fancy hyperlink things to that one place? It would seem to me >>> that would make updating it and finding it easier. It would seem that the >>> natural place would be in the WOLips wiki. I can see how having it spread >>> around makes extra documentation work and difficulties. >>> >>> Also, everything changes, but maybe the documentation can be set up to deal >>> with the changes better. For example, a writer could refer to the "current >>> version" throughout a document and maybe a note at the top would say "the >>> current recommended version is 4.5 (July 2014)" and so on. Updating the >>> document often would just be changing the 4.5 to 4.6, the date, July 2014 >>> to March 2015, etc. Anything to help keep the documentation easy to update >>> and provide clues as to what year the documentation was written. >> >> BTW, Confluence do display the last modified date of a page. But if we only >> fix a spelling mistake on a two years old document, it will put the date of >> the last modification. >> >>> >>> It is too bad we don't have IBM's Watson computer to read the mailing list, >>> extract the juicy bits, assemble a rough draft of documentation, and email >>> it to somebody for proof reading, probably to a "Dave". Next decade? >>> >>> >>> >>> On Jul 17, 2012, at 5:19 PM, G Brown wrote: >>> >>>> There is also: >>>> >>>> http://wiki.wocommunity.org/display/WOL/WOLips >>>> >>>> Getting Started >>>> The easiest way to install WOLips is to follow the steps in the Install >>>> WOLips with Eclipse Update Manager tutorial. If this is your first time >>>> using WOLips, this is the recommended method for installing WOLips. >>>> >>>> >>>> Also the installer should have a list of materials, or a page telling what >>>> all it does. >>>> >>>> >>>> On Jul 17, 2012, at 12:46 PM, Pascal Robert wrote: >>>> >>>>> I do agree that we need to have an installer that will install Eclipse, >>>>> WOLips, Wonder and the core WO frameworks. But we did cleanup the wiki a >>>>> lot a couple of months ago, so I would like to know which pages on the >>>>> wiki you followed, because this page: >>>>> >>>>> http://wiki.wocommunity.org/display/WONDER/Project+Wonder+Installation >>>>> >>>>> does specify that Java is not installed by default on Lion and launching >>>>> a Java app will install the JVM. >>>> >>>> >>>> G Brown >>>> gsbr...@umich.edu >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/webobjects-dev/gsbrown%40umich.edu >>>> >>>> This email sent to gsbr...@umich.edu >>> >>> >>> G Brown >>> gsbr...@umich.edu >>> >>> >>> >>> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/jeff%40netbrackets.com >> >> This email sent to j...@netbrackets.com > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/ken%40ksroom.com > > This email sent to k...@ksroom.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
