Put things wherever you want. Simply make the necessary adjustments in your wolips.properties. For deployment I strongly suggest include everything into your built app. This frees you from having to install any runtime env. I would suggest to keep the folder hierarchy conforming to the old standard with an arbitrary folder denoted as wo.local and inside it ./Library/Frameworks (giving wo.local.frameworks). Put a sub-folder called System into your chosen wo.local location and have wo.system point there. Inside wo.system have the same ./Library/Frameworks structure (giving you wo.system.frameworks). Note: these wo.xxx thingies are the entries from your wolips.properties
have fun ---markus--- > On 15.05.2016, at 00:19, Ken Anderson <[email protected]> wrote: > > OK everyone - hoping someone ca point me to an easy approach here. > > I’ve kept things around in /System/Library/WebObjects since the beginning - > just because, I don’t really know what’s looking there. But no it seems El > Capitan is going to make absolutely sure I can’t install anything in there. > > Anyone have a recommended place to place wotaskd, etc? I know I should > follow the rules - and they definitely make it difficult to work around them! > > Thanks, > Ken > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/mailinglists%40kataputt.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: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
