The ebuild needs to be updated to build the packages from source
I dunno. That's dodgy. I think I'm comfortable with the binaries myself, since half of the JDBC drivers in the tree will be binary-only anyway (Oracle, Informix, SQL Server, etc.) We haven't gotten to DB2 and Redbrick, etc yet. There are a bunch more binary-only JDBC drivers we haven't added. For consistency I think it's better to just use the bins for JDBC. We're more likely to get upstream support on them anyway.
I fixed the Bug concerning dev-java/jdb3-postgresql and found out that the jdbc2 classes are part of the jdbc3 classes. This is the point where it might not make sence to have different versions. I suggest to look at the ebuild for jdbc3-postgresql and look how the jdbc2jar file can be built wihtout having the jdbc3 classes still in the same jar (I think it was the Java Version that caused the decision whether to build jdc2 or jdbc3?). Here is the content of the jar file built with the jdbc3-postgresql-7.4.5.ebuild: META-INF/ META-INF/MANIFEST.MF org/ org/postgresql/ org/postgresql/Driver.class org/postgresql/PGConnection.class org/postgresql/PGNotification.class org/postgresql/PGRefCursorResultSet.class org/postgresql/PGStatement.class org/postgresql/core/ org/postgresql/core/BaseConnection.class org/postgresql/core/BaseResultSet.class org/postgresql/core/BaseStatement.class org/postgresql/core/Encoding.class org/postgresql/core/Field.class org/postgresql/core/Notification.class org/postgresql/core/PGStream.class org/postgresql/core/QueryExecutor.class org/postgresql/core/StartupPacket.class org/postgresql/fastpath/ org/postgresql/fastpath/Fastpath.class org/postgresql/fastpath/FastpathArg.class org/postgresql/geometric/ org/postgresql/geometric/PGbox.class org/postgresql/geometric/PGcircle.class org/postgresql/geometric/PGline.class org/postgresql/geometric/PGlseg.class org/postgresql/geometric/PGpath.class org/postgresql/geometric/PGpoint.class org/postgresql/geometric/PGpolygon.class org/postgresql/jdbc1/ org/postgresql/jdbc1/AbstractJdbc1Connection.class org/postgresql/jdbc1/AbstractJdbc1DatabaseMetaData.class org/postgresql/jdbc1/AbstractJdbc1ResultSet.class org/postgresql/jdbc1/AbstractJdbc1ResultSetMetaData.class org/postgresql/jdbc1/AbstractJdbc1Statement.class org/postgresql/jdbc2/ org/postgresql/jdbc2/AbstractJdbc2Blob.class org/postgresql/jdbc2/AbstractJdbc2Clob.class org/postgresql/jdbc2/AbstractJdbc2Connection.class org/postgresql/jdbc2/AbstractJdbc2DatabaseMetaData.class org/postgresql/jdbc2/AbstractJdbc2ResultSet$NullObject.class org/postgresql/jdbc2/AbstractJdbc2ResultSet$PrimaryKey.class org/postgresql/jdbc2/AbstractJdbc2ResultSet.class org/postgresql/jdbc2/AbstractJdbc2ResultSetMetaData.class org/postgresql/jdbc2/AbstractJdbc2Statement.class org/postgresql/jdbc2/Array.class org/postgresql/jdbc2/PBatchUpdateException.class org/postgresql/jdbc2/optional/ org/postgresql/jdbc2/optional/BaseDataSource.class org/postgresql/jdbc2/optional/ConnectionPool.class org/postgresql/jdbc2/optional/PGObjectFactory.class org/postgresql/jdbc2/optional/PooledConnectionImpl$ConnectionHandler.class org/postgresql/jdbc2/optional/PooledConnectionImpl$StatementHandler.class org/postgresql/jdbc2/optional/PooledConnectionImpl.class org/postgresql/jdbc2/optional/PoolingDataSource$1.class org/postgresql/jdbc2/optional/PoolingDataSource.class org/postgresql/jdbc2/optional/SimpleDataSource.class org/postgresql/jdbc3/ org/postgresql/jdbc3/AbstractJdbc3Blob.class org/postgresql/jdbc3/AbstractJdbc3Clob.class org/postgresql/jdbc3/AbstractJdbc3Connection.class org/postgresql/jdbc3/AbstractJdbc3DatabaseMetaData.class org/postgresql/jdbc3/AbstractJdbc3ResultSet.class org/postgresql/jdbc3/AbstractJdbc3Statement.class org/postgresql/jdbc3/Jdbc3Blob.class org/postgresql/jdbc3/Jdbc3CallableStatement.class org/postgresql/jdbc3/Jdbc3Clob.class org/postgresql/jdbc3/Jdbc3Connection.class org/postgresql/jdbc3/Jdbc3ConnectionPool.class org/postgresql/jdbc3/Jdbc3DatabaseMetaData.class org/postgresql/jdbc3/Jdbc3ObjectFactory.class org/postgresql/jdbc3/Jdbc3PooledConnection.class org/postgresql/jdbc3/Jdbc3PoolingDataSource.class org/postgresql/jdbc3/Jdbc3PreparedStatement.class org/postgresql/jdbc3/Jdbc3RefCursorResultSet.class org/postgresql/jdbc3/Jdbc3ResultSet.class org/postgresql/jdbc3/Jdbc3ResultSetMetaData.class org/postgresql/jdbc3/Jdbc3SimpleDataSource.class org/postgresql/jdbc3/Jdbc3Statement.class org/postgresql/largeobject/ org/postgresql/largeobject/BlobInputStream.class org/postgresql/largeobject/BlobOutputStream.class org/postgresql/largeobject/LargeObject.class org/postgresql/largeobject/LargeObjectManager.class org/postgresql/util/ org/postgresql/util/MD5Digest.class org/postgresql/util/MessageTranslator.class org/postgresql/util/PGbytea.class org/postgresql/util/PGmoney.class org/postgresql/util/PGobject.class org/postgresql/util/PGtokenizer.class org/postgresql/util/PSQLException.class org/postgresql/util/PSQLState.class org/postgresql/util/UnixCrypt.class org/postgresql/errors.properties org/postgresql/errors_de.properties org/postgresql/errors_fr.properties org/postgresql/errors_it.properties org/postgresql/errors_nl.properties org/postgresql/errors_pt_BR.properties org/postgresql/errors_ru.properties org/postgresql/errors_zh_TW.properties
This bug should be closed as we cannot build JDBC 2.0 driver from source because it needs JDK 1.3 which is not in portage (and never will be). Currently there is jdbc3-postgresql driver in portage which is JDBC 3.0 driver. You can also see bug 157973 for newest driver as of this date.
Closing bug since we can't and won't fix.
