<div>Yup that what I plan. I am trying to do a clean build manually in a workspace for me to understand how things are wired as an user.</div>
<div> </div>
<div>Thanks</div>
<div> </div>
<div>Sanjay<br><br></div>
<div class="gmail_quote">On Tue, Oct 20, 2009 at 10:27 AM, Larry O'Leary <span dir="ltr"><<a href="mailto:loleary@redhat.com">loleary@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="h5">On Tue, 2009-10-20 at 10:11 -0500, Ramesh Reddy wrote:<br>> Sanjay,<br>><br>> The "teiid-connector-sdk" provides a "execution" environment for a<br>> connector during development of a connector. Based on the road map we<br>
> may not want to use this at all, and directly use the Teiid runtime to<br>> test a connector.<br>><br>> So, no to using cdk/lib. Yes, to use the "jars" directly. To start with<br>> you can make it as user's responsibility to add this. If you want to get<br>
> this automated, then we can think of making this a "maven" based<br>> project, and just provide the dependencies in "pom.xml" and then they<br>> will be downloaded from JBoss maven repository automatically, as all<br>
> these libraries will be available though maven repository.<br>><br>> Also note "teiid-connector-sdk-6.2.0-SNAPSHOT.jar" is only currently<br>> used for unit tests. The developer who is working with your plugin may<br>
> not have the Teiid source at all, all he got is your plugin and a<br>> document and he needs to build and test connector.<br>><br>> Thanks. Good questions keep em coming.<br>><br>> Ramesh..<br>><br>
> On Tue, 2009-10-20 at 02:24 -0500, Sanjay Chaudhuri wrote:<br>> > Hi Ramesh,<br>> ><br>> > Can you please let me know the jars would contain the following<br>> > classes ?<br>> ><br>> > org.teiid.dqp.internal.datamgr.impl.FakeExecutionContextImpl<br>
> > com.metamatrix.core.util.UnitTestUtil<br>> > com.metamatrix.query.metadata.QueryMetadataInterface<br>> > com.metamatrix.query.unittest.FakeMetadataFacade<br>> > com.metamatrix.query.unittest.FakeMetadataFactory<br>
> > com.metamatrix.query.unittest.FakeMetadataObject<br>> > com.metamatrix.query.unittest.FakeMetadataStore<br>> ><br>> > As part of the CDK classpath, do I take all the jars from the cdk/lib<br>> > directory or just use teiid-connector-sdk-6.2.0-SNAPSHOT.jar and<br>
> > teiid-engine-6.2.0-SNAPSHOT.jar &<br>> > teiid-connector-api-6.2.0-SNAPSHOT.jar ? Also<br>> > teiid-connector-api-6.2.0-SNAPSHOT.jar is in the teiid distribution<br>> > package and not in cdk/lib directory of the cdk kit. This kind of<br>
> > defeats my plan to use the cdk kit as-is to register as a contributor<br>> > sdk with version through extension point unless I manually copy it and<br>> > make it a distribution. Using cdk kit as-is would facilitate choosing<br>
> > any version of cdk from more than one avaiable versions at runtime.<br><br></div></div>Is there anyway we can not have the connector developer's plug-in depend<br>on teiid-engine? It seems that such a dependency wouldn't adhere to the<br>
connector-api itself. In my opinion the only thing a connector should<br>be dependent on is the API. It would be nice however to offer a unit<br>test package base to the connector developer so that their connector<br>could be easily integrated with a connector test framework.<br>
<br>----<br><font color="#888888">Larry<br><br></font></blockquote></div><br>