We've actually been through all of this before. It's actually worse to
have the jdbc drivers included. The problem is that people run and
deploy with it and find weird problems if the version in ofbiz doesn't
match the database version. The result is production down time and
repeated mailing list questions.
So the answer, again, is: no, we have decided as a community to not
include these jars. Unless the issues above as resolved that will NOT
change.
-David
On Nov 23, 2008, at 13:40, Harmeet Bedi <
[hidden email]> wrote:
> Maybe a good part way would be to support only popular opensource
> out of box. You have one - derby. The other 2 mains ones are
> postgres and mysql.
>
> We have the problem addressed on our end, that is not the concern.
> Was trying to see if we can generalize and reduce both our and
> other's pain. Not a big thing just makes life a bit easier.
>
>
> On 11/23/08 1:17 PM, Adrian Crum wrote:
>> I think this issue was addressed a few days ago. OFBiz does not
>> include jdbc drivers because there are too many databases and too
>> many versions.
>>
>> If you find copying a single file difficult, perhaps you could
>> create a script or something to do it automatically.
>>
>> -Adrian
>>
>>
>> --- On Sun, 11/23/08, Harmeet Bedi <
[hidden email]> wrote:
>>
>>
>>> From: Harmeet Bedi <
[hidden email]>
>>> Subject: request to add missing jdbc jars, at least postgres.jar
>>> To:
[hidden email]
>>> Date: Sunday, November 23, 2008, 9:58 AM
>>> /framework/entity/lib contains only derby jdbc library.
>>> Wondering if it makes sense to enhance it to include other
>>> popular jar files.
>>> We run ofbiz against postgres and have to copy the jar
>>> file.
>>>
>>> It should be easy to add popular jdbc jar files at least
>>> when requested by someone who needs it. Won't cause
>>> conflicts and make life easier for people working on ofbiz.
>>>
>>> If this seems ok.. and if you want i can file an issue and
>>> attach the most appropriate current postgres jar to issue.
>>>
>>> Harmeet
>>>
>>
>>
>>
>
Locked
