If the client jar is in a known location in the system (i.e. exposed by a plug-in, in a
path accessible from a system variable, or whatever), you can actually save the user a
step and supply that path automagically.
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "John Doyle" <jdoyle(a)redhat.com>
To: "Andersen Max" <max.andersen(a)redhat.com>
Sent: Monday, April 26, 2010 11:59:06 AM GMT -07:00 US/Canada Mountain
Subject: Re: [jbosstools-dev] Repository location for new eclipse feature.
It only depends upon DTP. The DTP connectivity framework lets you plug in to tweak the
DTP framework for your specific connection URL, SQL semantics, etc, but there is no build
dependency on any Teiid resources. The user has to browse to the client jar when they use
the feature in order to connect and execute.
----- "Andersen Max" <max.andersen(a)redhat.com> wrote:
Does this implementation not have any dependency on Teeid and thus
something that is a natural part of Teed Designer eclipse feature, or
On Apr 26, 2010, at 16:35, John Doyle wrote:
> I'm working on a Eclipse DTP connectivity implementation for Teiid.
My expectation for these plug-ins is that they will eventually be
delivered with JBoss Tools and Dev Studio, but initially they will be
delivered as a required feature with the Teiid Designer. The feature
only depends upon Eclipse DTP, so it could be used in any DTP
> I'm looking for advice on where I should check this code in
permanently in order to support all of these delivery options. If
these plugins have their own Athena/Hudson build do you think it's
appropriate to check them into the JBoss tools repos?
> jbosstools-dev mailing list
jbosstools-dev mailing list