Hi Hugi, On 29 Apr 2016, at 12:10 am, Hugi Thordarson <[email protected]> wrote:
>> Can I just clarify this issue with Properties by asking a few specific >> questions? >> >> 1. I take it that the usual Properties precedence works as designed for >> Properties in the application bundle—there are no surprises here, right? It >> will find Properties, and then Properties.dev in development mode, and >> Properties.foo for -Duser.name=foo? > > Yes, this works exactly as before, as far as I can tell. > >> 2. What are people doing in the real world for framework-level Properties in >> both development and deployment? This would be a bit of a show-stopper for >> us—we use framework-level Properties fairly widely, for example to set >> default values that often don’t need to be overridden at the app level. >> >> Is this a big deal, or is there a straightforward solution? > > Now… Framework Properties seem to work fine for me. I just verified that by > creating a Properties file in one of my frameworks with a property, deploying > a dependent app and checking the property’s value. Worked fine. Overrode the > same property in the application’s Properties file—also works fine. > > Not sure why it works for me. Perhaps someone can shed some light on it? I’m > using Wonder v. 7.0.0-SNAPSHOT. Thanks for the info Hugi. I haven’t got as far as deploying a test app yet, but that sounds promising. -- Paul Hoadley http://logicsquad.net/ _______________________________________________ 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]
