Hi Johnny, On 15/08/2013, at 10:14 AM, Johnny Miller <[email protected]> wrote:
> Please see my last email about not having the PostgreSQL plugin in the > application itself. I have different EOModels in individual frameworks and > then the application includes those frameworks. The frameworks have the > PostgreSQL plugin but the actual application itself didn't include the > PostgreSQL plugin. When I included it it worked as expected (at least > locally). > > I'm uploading my application now to test. Does that make any sense to you? Obviously the PostgresqlPlugIn is, itself, just a framework. I suspect what you're running into here is that framework inclusion is not transitive. That is, having PostgresqlPlugIn.framework on the build path of some framework F does not make the plug-in available to application A just because F is on A's build path. If A needs or is expecting the plug-in, it needs to be on A's build path. Are you building A with frameworks embedded? Does PostgresqlPlugIn.framework even make it into A's bundle? -- 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]
