On May 10, 2011, at 12:05 PM, Michael Schrag wrote: > > > Sent from my iPad > > On May 10, 2011, at 6:47 AM, Henrique Gomes <[email protected]> wrote: > >> It's always good to minimize confusion, I'm all for it. >> >> On May 9, 2011, at 11:00 AM, Pascal Robert wrote: >> >>> Ok, so we have four pages in the wiki that tells how to configure Apache >>> for development, and numerous pages on how to install WOLips and the core >>> WO frameworks. We need one or two pages maximum! So we need to define what >>> is the The One True Way to install and configure everything for development. >>> >>> My personal preferences are: >>> >>> * Install WO in /Developer/WebObjects with woinstall.jar >>> >>> I think installing WO with the Apple dmg is unsafe, because it install >>> stuff in /System, and Apple have been know to remove stuff they don't >>> support or third-party tools from /System when new releases of OS X are >>> made. Installing everything in /Developer/WebObjects or /Library/WebObjects >>> is much safer. >>> >> That's something I never thought about, never experienced, I'll take note >> of it. >> I just have a problem with woinstall: it does not work trough an http proxy >> and that has made my life complicated in the past when deploying on >> customers which restrict http access. Maybe it could be changed so that the >> users downloads the .dmg and then points woinstall to it? > The source for this is trivial. If java supports the type of proxy you have, > this should work with almost no effort. I don't recall if we use the java.net > API or apache httpclient, but I it's java, you can just set the standard -D > proxy system properties when you run and it should work. If it's apache, it > may require two lines of code. Patches welcome.
No patch needed, on the mac it uses the proxy from network settings, on linux the standard http_proxy env variable does not work, it requires the system properties: java -Dhttp.proxyHost=proxyHostName -Dhttp.proxyPort=portNumber -jar WOInstaller.jar 5.4.3 t The knowledge about those those -D options must have been in a part of my brain that was off-line when I was deploying.... > >> >>> * Install Eclipse/WOLips with Golipse >>> >>> IMHO, that's the best way to install the tools, since they install all >>> required plugins + the correct version of Eclipse. But since the default >>> WOLips properties are set for /Library and /System, we would need to change >>> them to /Developer/WebObjects when installing from Golipse. >>> >> >> I might be the only one, but I like to have some control of my machine, and >> really see no point in those scripts. >> Just tell what version and package of eclipse to install (classic, Java, >> whatever) and list the plugin sites. >> We are talking to *developers*... about using a complex framework. > Total crazy talk. Why take 10 minutes to do something that you can do in 5 > seconds? And if we're talking about "developers" you can either edit the > script or look in it to get your urls and plugins. I originally wrote the > base script for myself, because I got tired of wasting my time doing > repetitive robot work. > > ms > OK, I'm the only one then :-) Henrique Gomes _______________________________________________ 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]
