Hello, Just resurrecting a thread from seven months ago as I finally bite the Maven bullet and attempt to get my own HelloWorld off the ground…
On 18 Sep 2015, at 7:58 am, Ramsey Gurley <[email protected]> wrote: > So I need to copy all the properties from all the frameworks into my app’s > properties file? And in production, if I compile to a jar, I then need to > list all the properties as command line arguments? > > Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my > project’s maven properties, but if I set a breakpoint in this class, it’s > looking for the class in the m2 repository. Is there some other thing I need > to do to make the application use the ERExtensions in my workspace? > > On Sep 17, 2015, at 2:27 PM, G Brown <[email protected] > <mailto:[email protected]>> wrote: > >> >>> I also get quite a lot of these properties warnings in the console: >>> >>> Sep 17 11:24:16 helloworld[50191] WARN >>> er.extensions.foundation.ERXFileUtilities - Can't get path when run as >>> jar: JavaFoundation - Properties >>> Sep 17 11:24:16 helloworld[50191] WARN >>> er.extensions.foundation.ERXFileUtilities - Can't get path when run as >>> jar: JavaFoundation - Properties.dev >>> Sep 17 11:24:16 helloworld[50191] WARN >>> er.extensions.foundation.ERXFileUtilities - Can't get path when run as >>> jar: JavaFoundation - Properties.rgurley >>> >>> And so on for basically every framework. >> >> WebObjects works with jar type frameworks; Wonder expects non-jar or file >> based frameworks, at least er.extensions.foundation.ERXFileUtilities >> expects them. >> So properties contained in Wonder frameworks have to be set in your >> properties file, as ERXFileUtilities is used often to read the properties. >> >> G Brown >> [email protected] <mailto:[email protected]> 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? 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? -- 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]
