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.
Created attachment 68718 [details] jdbm-1.0-buildfile.patch
Some unit tests fail here: https://overlays.gentoo.org/svn/proj/java/migrated-java-experimental-overlay/dev-java/jdbm
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.
