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 252097 - Review Request: gnu-trove - High performance collections for Java
Summary: Review Request: gnu-trove - High performance collections for Java
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://trove4j.sourceforge.net/
Whiteboard:
Depends On:
Blocks: FE-DEADREVIEW
TreeView+ depends on / blocked
 
Reported: 2007-08-13 22:05 UTC by Vivek Lakshmanan
Modified: 2008-06-26 01:08 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Vivek Lakshmanan 2007-08-13 22:05:53 UTC
Spec URL: http://vivekl.fedorapeople.org/rpms/gnu-trove.spec
SRPM URL: http://vivekl.fedorapeople.org/rpms/gnu-trove-1.0.2-5jpp.1.fc8.src.rpm

The GNU Trove library has two objectives:

Provide "free" (as in "free speech" and "free beer"),
fast, lightweight implementations of the java.util
Collections API. These implementations are designed
to be pluggable replacements for their JDK equivalents.

Whenever possible, provide the same collections support
for primitive types. This gap in the JDK is often
addressed by using the "wrapper" classes
(java.lang.Integer, java.lang.Float, etc.) with
Object-based collections. For most applications, however,
collections which store primitives directly will require
less space and yield significant performance gains.
Needed for supporting application servers

Comment 1 Jason Tibbitts 2008-06-26 01:08:21 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.