> I think this aspect is holding up the ebuilds. Not really sure what's
> holding them up. I have yet to post a jdbc2 till I get the ebuild
> squared away for jdbc3. Since 2 is just like 3 but with native stuff.

Sorry, it might be that we have misunderstanding here... jdbc2 is "JDBC 2.0"
or "jdbc type 2" driver? if latter, then you have to rename jdbc3 into
jdbc4, since "jdbc type 3" driver is the one that has a server-side
component that uses JNI to talk to the database server, but has its own wire
protocol to talk to the client-side jars.

Roman