obey the bunny!



On Jul 18, 2012, at 5:22 PM, [email protected] wrote:

> Hi WOrriors, 
> 
> Sorry for the cross post but it seems these days most questions get asked on 
> the Apple lists regardless if they are pure Apple related or WOLips / Eclipse 
> / WOnder related. 
> 
> Anyone have some advice for me? I'd like to put my EOModel files into 
> "Resources/model" but fluffy bunny isn't happy. Do I have any recourse or 
> must I obey the bunny? 
> 
> Many thanks, 
> -- Aaron 
> 
> ----- Forwarded by Aaron Rosenzweig/hq/hjf on 07/18/2012 05:20 PM ----- 
> 
> From:        Aaron Rosenzweig/hq/hjf 
> To:        Wonder Project <[email protected]> 
> Date:        07/16/2012 03:40 PM 
> Subject:        Fluffy Bunny question 
> 
> 
> Hi WOrriors, 
> 
> I have an app and a separate WO framework. All my EO model files are in the 
> "Resources" directory of the framework. 
> 
> In Eclipse, when I run the app, everything is fine. 
> 
> When I make a "Resources/model" folder in the framework and then move the EO 
> model files into it, I can no longer run my app within Eclipse. The various 
> EO model files cannot be found. 
> 
> Ok, so this is not-so-fluffy bunny but what if I really want to put 
> everything in "Resources/model" at least during development? Where do I go to 
> make this happen? Is it in WOlips itself or some XML file? 
> 
> Many thanks for any tips or pointers, 
> -- Aaron _______________________________________________
> 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/jtayler%40oeinc.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]

Reply via email to