Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 252116 - Review Request: berkeleydb - Berkeley DB Java Edition
Summary: Review Request: berkeleydb - Berkeley DB Java Edition
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL: http://www.sleepycat.com/products/bdb...
Whiteboard:
Depends On:
Blocks: FE-DEADREVIEW
TreeView+ depends on / blocked
 
Reported: 2007-08-13 22:32 UTC by Vivek Lakshmanan
Modified: 2008-06-26 01:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-26 01:13:45 UTC


Attachments (Terms of Use)

Description Vivek Lakshmanan 2007-08-13 22:32:07 UTC
Spec URL: http://vivekl.fedorapeople.org/rpms/berkeleydb.spec
SRPM URL: http://vivekl.fedorapeople.org/rpms/berkeleydb-2.0.90-1jpp.2.fc8.src.rpm

Berkeley DB Java Edition is a high performance, transactional
storage engine written entirely in Java. Like the highly
successful Berkeley DB product, Berkeley DB Java Edition
executes in the address space of the application, without
the overhead of client/server communication. It stores data
in the application's native format, so no runtime data
translation is required. Berkeley DB Java Edition supports
full ACID transactions and recovery. It provides an easy-to-use,
programmatic interface, allowing developers to store and
retrieve information quickly, simply and reliably.
Needed for supporting application servers

Comment 1 Jason Tibbitts 2008-06-26 01:13:45 UTC
Closing as detailed in bug 252049 after a complete lack of response.



Note You need to log in before you can comment on or make changes to this bug.