[
https://issues.apache.org/jira/browse/CASSANDRA-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050884#comment-13050884
]
Rick Shaw commented on CASSANDRA-2761:
--------------------------------------
{quote}
What are these 50 other class dependencies? Where are they being drug in?
{quote}
- o.a.c.db.marshall.*
-- 23 various classes
- o.a.c.utils.ByteBufferUtil
-- org.apache.cassandra.io.util.FileDataInput
-- org.apache.cassandra.io.util.FileUtils
- o.a.c.config.ColumnDefinition
- o.a.c.config.CFMetaData
-- org.apache.cassandra.cache.IRowCacheProvider;
-- org.apache.cassandra.db.migration.avro.ColumnDef
-- org.apache.cassandra.db.ColumnFamilyType;
--- org.apache.cassandra.concurrent.JMXEnabledThreadPoolExecutor
--- org.apache.cassandra.config.DatabaseDescriptor
---- org.apache.cassandra.auth.AllowAllAuthenticator
---- org.apache.cassandra.auth.AllowAllAuthority
---- org.apache.cassandra.auth.IAuthenticator
---- org.apache.cassandra.auth.IAuthority
---- org.apache.cassandra.config.Config.RequestSchedulerId
---- org.apache.cassandra.db.ColumnFamilyStore
----- 13 new items
---- org.apache.cassandra.db.ColumnFamilyType
---- org.apache.cassandra.db.DefsTable
----- org.apache.cassandra.config.DatabaseDescriptor;
----- org.apache.cassandra.config.KSMetaData;
----- org.apache.cassandra.db.filter.QueryFilter;
----- org.apache.cassandra.db.filter.QueryPath;
----- org.apache.cassandra.db.migration.Migration;
----- org.apache.cassandra.io.SerDeUtils;
----- org.apache.cassandra.service.StorageService;
----- org.apache.cassandra.utils.ByteBufferUtil;
----- org.apache.cassandra.utils.UUIDGen;
---- org.apache.cassandra.db.migration.Migration
---- org.apache.cassandra.dht.IPartitioner
---- org.apache.cassandra.io.sstable.Descriptor
---- org.apache.cassandra.io.util.FileUtils
---- org.apache.cassandra.locator.*
---- org.apache.cassandra.scheduler.IRequestSchedule;
---- org.apache.cassandra.scheduler.NoScheduler
--- org.apache.cassandra.db.compaction.CompactionManager
--- org.apache.cassandra.db.filter.QueryFilter
--- org.apache.cassandra.db.filter.QueryPath
--- org.apache.cassandra.dht.IPartitioner
--- org.apache.cassandra.dht.Range
--- org.apache.cassandra.gms.FailureDetector
--- org.apache.cassandra.gms.Gossiper
--- org.apache.cassandra.gms.ApplicationState
--- org.apache.cassandra.net.MessagingService
---- 10 new classes
--- org.apache.cassandra.service.*
--- org.apache.cassandra.utils.WrappedRunnable
-- org.apache.cassandra.db.HintedHandOffManager;
-- org.apache.cassandra.db.SystemTable;
-- org.apache.cassandra.db.Table;
-- org.apache.cassandra.db.ColumnFamilyStore;
-- org.apache.cassandra.db.migration.Migration;
-- org.apache.cassandra.db.compaction.AbstractCompactionStrategy;
-- org.apache.cassandra.io.SerDeUtils;
-- org.apache.cassandra.utils.Pair;
- o.a.c.config.ConfigurationException
The point is there are lots and they are scattered all over the various
packages; It will be very difficult to manage when they change from the driver
package (client side), which is supposed to be able to change independent of
the server code. If a subset of the server code is to be a dependency then that
subset (jar/s) must be managed in the main build not the driver build.
{quote}
What would you call such a jar? When I looked at this, there didn't seem to be
any delineation that made sense.
{quote}
I agree it is not any clear set of packages. They are scattered all over.
As to a name for the jar... I'm not a good namer in the best of circumstances
but I think the intent is to pick those files that are used in common between
client and server. I guess I'd use that as the basis for the name.
> JDBC driver does not build
> --------------------------
>
> Key: CASSANDRA-2761
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2761
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 1.0
> Reporter: Jonathan Ellis
> Assignee: Rick Shaw
> Fix For: 1.0
>
> Attachments: jdbc-driver-build-v1.txt
>
>
> Need a way to build (and run tests for) the Java driver.
> Also: still some vestigal references to drivers/ in trunk build.xml.
> Should we remove drivers/ from the 0.8 branch as well?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
