Aha! Thanks for the workaround.
I think the bug is that setting
"eoAdaptorClassName=com.paizo.jdbcadaptor.DistributedJDBCAdaptor" in
build.properties isn't getting used in the ant builds. It looks like
this is the same as setting the EOAdaptor Class field on the WOLips
Build properties for the project via the gui.
On Jan 7, 2008, at 5:47 PM, Andrew Lindesay wrote:
> Hello Gary;
>
> I do something like this in my ant build file -- is that what you
> mean?
>
>> <woframework
>> name="${framework.name}"
>> destDir="${dest.dir}"
>>
>> customInfoPListContent="<key>EOAdaptorClassName</
>> key><string>nz.co.lindesay.openbasejdbcadaptor.LEEOOpenbaseJ
>> DBCAdaptor</string>"
>> principalClass=""
>> eoAdaptorClassName="">
>>
>> ...
>>
>> </woframework>
>
> ...it comes out looking like this...
>
>> ...
>> <string></string>
>> <key>CFBundlePackageType</key>
>> <string>FMWK</string>
>>
>> <key>EOAdaptorClassName</
>> key><string>nz.co.lindesay.openbasejdbcadaptor.LEEOOpenbaseJDBCAdapto
>> r</string>
>> </dict>
>> </plist>
>
> cheers.
>
> On 8/01/2008, at 1:58 PM, Gary Teter wrote:
>
>> The key EOAdaptorClassName is not being set in the Info.plist file
>> created during an ant build. (It is properly created in the
>> Info.plist maintained by the WOLips incremental builder, so this
>> isn't a problem during development, but it is during deployment.)
>
> ___
> Andrew Lindesay
> technology : www.lindesay.co.nz
> business : www.silvereye.co.nz
>
>
>
-- WireHose: Smart metadata and personalization for WebObjects. http://wirehose.com/
This archive was generated by hypermail 2.0.0 : Mon Jan 07 2008 - 20:54:14 EST