Bug 106343

Summary:	dev-java/mapdb - Concurrent Maps, Sets and Queues backed by disk storage or off-heap-memory. (was: =dev-java/jdbm-1.0 is available)
Product:	Gentoo Linux	Reporter:	Gunnar Wrobel (RETIRED) <wrobel>
Component:	New packages	Assignee:	Java team <java>
Status:	RESOLVED OBSOLETE
Severity:	enhancement	Keywords:	EBUILD
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://github.com/jankotek/mapdb
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	jdbm-1.0-buildfile.patch

Description Gunnar Wrobel (RETIRED) gentoo-dev

2005-09-18 01:38:25 UTC

The ebuild just needs a version bump to 1.0 and the patch for the build.xml
needs only minor modifications. I attached the modified patch.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Gunnar Wrobel (RETIRED) gentoo-dev

2005-09-18 01:39:08 UTC

Created attachment 68718 [details]
jdbm-1.0-buildfile.patch

Comment 2 Petteri Räty (RETIRED) gentoo-dev

2007-01-25 22:25:43 UTC

Some unit tests fail here:
https://overlays.gentoo.org/svn/proj/java/migrated-java-experimental-overlay/dev-java/jdbm

Comment 3 Tom Wijsman (TomWij) (RETIRED) gentoo-dev

2013-11-24 23:35:28 UTC

http://jdbm.sourceforge.net/
--> https://github.com/jankotek/JDBM3
--> https://github.com/jankotek/JDBM4
--> https://github.com/jankotek/mapdb

JDBM is quite old (reported in 2005, this bug last touched in 2007) and I doubt if it in still needed these days; therefore, we can bring MapDB (releases every month, last commit some days ago), which is its successor, to the Portage tree.

If someone still sees an use in the old JDBM and can fix it up, I suggest to file a new bug with fixed ebuilds and/or patches attached; see Comment #2 as to why it is broken. I however also suggest that we should look at removing JDBM from the Portage tree at some point after we have brought MapDB to the Portage tree.