On Tue, 2009-10-20 at 10:11 -0500, Ramesh Reddy wrote:
> Sanjay,
>
> The "teiid-connector-sdk" provides a "execution" environment for a
> connector during development of a connector. Based on the road map we
> may not want to use this at all, and directly use the Teiid runtime to
> test a connector.
>
> So, no to using cdk/lib. Yes, to use the "jars" directly. To start with
> you can make it as user's responsibility to add this. If you want to get
> this automated, then we can think of making this a "maven" based
> project, and just provide the dependencies in "pom.xml" and then they
> will be downloaded from JBoss maven repository automatically, as all
> these libraries will be available though maven repository.
>
> Also note "teiid-connector-sdk-6.2.0-SNAPSHOT.jar" is only currently
> used for unit tests. The developer who is working with your plugin may
> not have the Teiid source at all, all he got is your plugin and a
> document and he needs to build and test connector.
>
> Thanks. Good questions keep em coming.
>
> Ramesh..
>
> On Tue, 2009-10-20 at 02:24 -0500, Sanjay Chaudhuri wrote:
> > Hi Ramesh,
> >
> > Can you please let me know the jars would contain the following
> > classes ?
> >
> > org.teiid.dqp.internal.datamgr.impl.FakeExecutionContextImpl
> > com.metamatrix.core.util.UnitTestUtil
> > com.metamatrix.query.metadata.QueryMetadataInterface
> > com.metamatrix.query.unittest.FakeMetadataFacade
> > com.metamatrix.query.unittest.FakeMetadataFactory
> > com.metamatrix.query.unittest.FakeMetadataObject
> > com.metamatrix.query.unittest.FakeMetadataStore
> >
> > As part of the CDK classpath, do I take all the jars from the cdk/lib
> > directory or just use teiid-connector-sdk-6.2.0-SNAPSHOT.jar and
> > teiid-engine-6.2.0-SNAPSHOT.jar &
> > teiid-connector-api-6.2.0-SNAPSHOT.jar ? Also
> > teiid-connector-api-6.2.0-SNAPSHOT.jar is in the teiid distribution
> > package and not in cdk/lib directory of the cdk kit. This kind of
> > defeats my plan to use the cdk kit as-is to register as a contributor
> > sdk with version through extension point unless I manually copy it and
> > make it a distribution. Using cdk kit as-is would facilitate choosing
> > any version of cdk from more than one avaiable versions at runtime.
Is there anyway we can not have the connector developer's plug-in depend