Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DTP » ecore ODA - dependencies for driver?
ecore ODA - dependencies for driver? [message #45011] Sat, 07 June 2008 06:39 Go to next message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1340
Registered: July 2009
Senior Member
Hi,

Really excited about the ecore ODA driver, scratches a big itch. For my
usage, all of the setup will be done programmatically -- I'll be using
it as a front end for charting of live models. So for packaging
purposes I'm wondering what dependnecies the ODA driver alone will
have. That is, does it need the BIRT designer, EMF Transaction, DTP
JDBC, etc..? Basically, do you envision having a fully p2 capable
(whatever that might mean :)) update site that grabs what's needed?
Trying to avoid dependency trauma for my users..
Re: ecore ODA - dependencies for driver? [message #45122 is a reply to message #45011] Tue, 10 June 2008 22:53 Go to previous messageGo to next message
Jeff Ramsdale is currently offline Jeff RamsdaleFriend
Messages: 122
Registered: July 2009
Senior Member
Hi Miles,

Thanks for your interest!

This is the list of dependencies for the Ecore ODA driver itself (i.e.
not the UI):

org.eclipse.core.resources
org.eclipse.core.runtime
org.eclipse.datatools.connectivity.oda
org.eclipse.datatools.connectivity.oda.design
org.eclipse.datatools.connectivity.oda.profile
org.eclipse.emf.ecore.xmi
org.eclipse.emf.query.ocl
org.eclipse.ocl.ecore

These, of course, do have transitive dependencies.

For the near term I don't see having the Ecore ODA Driver available on
an update site. While we'd love to get there we have limited time to get
to our backlog and that might be a big step. We're the first project in
the DTP Incubator and there would need to be some infrastructure set up
and coordination with the rest of the community. There's also the issue
that we depend on EMF 2.3 and Java 5, which is a constraint the rest of
the DTP family isn't subject to.

We'd be interested in hearing about your experiences with the Driver
(and recommendations/bug reports if you have them).

-jeff

Miles Parker wrote:
>
> Hi,
>
> Really excited about the ecore ODA driver, scratches a big itch. For my
> usage, all of the setup will be done programmatically -- I'll be using
> it as a front end for charting of live models. So for packaging purposes
> I'm wondering what dependnecies the ODA driver alone will have. That is,
> does it need the BIRT designer, EMF Transaction, DTP JDBC, etc..?
> Basically, do you envision having a fully p2 capable (whatever that
> might mean :)) update site that grabs what's needed? Trying to avoid
> dependency trauma for my users..
>
Re: ecore ODA - dependencies for driver? [message #45870 is a reply to message #45122] Fri, 27 June 2008 20:28 Go to previous message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1340
Registered: July 2009
Senior Member
Just getting back to this.. glad to hear it -- the dependencies are
perfect for me as I'm already using EMF (duh) and some of EMFT -- I'll
just have to look into ODA. And natch no prob. w/ EMF 2.3 Java 5, my
target is Gany. That is if I I read you correctly to say EMF 2.3+.

w/ this limited tree its np on update site -- assuming you guys
wouldn't have a problem w/ my including relevant jars in my distro /
update site.

(It may. be a while before I can get to this..I have a long list of
tasks.. :))

On 2008-06-10 14:53:36 -0800, Jeff Ramsdale <jeff.ramsdale@gmail.com> said:

> Hi Miles,
>
> Thanks for your interest!
>
> This is the list of dependencies for the Ecore ODA driver itself (i.e.
> not the UI):
>
> org.eclipse.core.resources
> org.eclipse.core.runtime
> org.eclipse.datatools.connectivity.oda
> org.eclipse.datatools.connectivity.oda.design
> org.eclipse.datatools.connectivity.oda.profile
> org.eclipse.emf.ecore.xmi
> org.eclipse.emf.query.ocl
> org.eclipse.ocl.ecore
>
> These, of course, do have transitive dependencies.
>
> For the near term I don't see having the Ecore ODA Driver available on
> an update site. While we'd love to get there we have limited time to
> get to our backlog and that might be a big step. We're the first
> project in the DTP Incubator and there would need to be some
> infrastructure set up and coordination with the rest of the community.
> There's also the issue that we depend on EMF 2.3 and Java 5, which is a
> constraint the rest of the DTP family isn't subject to.
>
> We'd be interested in hearing about your experiences with the Driver
> (and recommendations/bug reports if you have them).
>
> -jeff
>
> Miles Parker wrote:
>>
>> Hi,
>>
>> Really excited about the ecore ODA driver, scratches a big itch. For my
>> usage, all of the setup will be done programmatically -- I'll be using
>> it as a front end for charting of live models. So for packaging
>> purposes I'm wondering what dependnecies the ODA driver alone will
>> have. That is, does it need the BIRT designer, EMF Transaction, DTP
>> JDBC, etc..? Basically, do you envision having a fully p2 capable
>> (whatever that might mean :)) update site that grabs what's needed?
>> Trying to avoid dependency trauma for my users..
Re: ecore ODA - dependencies for driver? [message #591332 is a reply to message #45011] Tue, 10 June 2008 22:53 Go to previous message
Jeff Ramsdale is currently offline Jeff RamsdaleFriend
Messages: 122
Registered: July 2009
Senior Member
Hi Miles,

Thanks for your interest!

This is the list of dependencies for the Ecore ODA driver itself (i.e.
not the UI):

org.eclipse.core.resources
org.eclipse.core.runtime
org.eclipse.datatools.connectivity.oda
org.eclipse.datatools.connectivity.oda.design
org.eclipse.datatools.connectivity.oda.profile
org.eclipse.emf.ecore.xmi
org.eclipse.emf.query.ocl
org.eclipse.ocl.ecore

These, of course, do have transitive dependencies.

For the near term I don't see having the Ecore ODA Driver available on
an update site. While we'd love to get there we have limited time to get
to our backlog and that might be a big step. We're the first project in
the DTP Incubator and there would need to be some infrastructure set up
and coordination with the rest of the community. There's also the issue
that we depend on EMF 2.3 and Java 5, which is a constraint the rest of
the DTP family isn't subject to.

We'd be interested in hearing about your experiences with the Driver
(and recommendations/bug reports if you have them).

-jeff

Miles Parker wrote:
>
> Hi,
>
> Really excited about the ecore ODA driver, scratches a big itch. For my
> usage, all of the setup will be done programmatically -- I'll be using
> it as a front end for charting of live models. So for packaging purposes
> I'm wondering what dependnecies the ODA driver alone will have. That is,
> does it need the BIRT designer, EMF Transaction, DTP JDBC, etc..?
> Basically, do you envision having a fully p2 capable (whatever that
> might mean :)) update site that grabs what's needed? Trying to avoid
> dependency trauma for my users..
>
Re: ecore ODA - dependencies for driver? [message #591600 is a reply to message #45122] Fri, 27 June 2008 20:28 Go to previous message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1340
Registered: July 2009
Senior Member
Just getting back to this.. glad to hear it -- the dependencies are
perfect for me as I'm already using EMF (duh) and some of EMFT -- I'll
just have to look into ODA. And natch no prob. w/ EMF 2.3 Java 5, my
target is Gany. That is if I I read you correctly to say EMF 2.3+.

w/ this limited tree its np on update site -- assuming you guys
wouldn't have a problem w/ my including relevant jars in my distro /
update site.

(It may. be a while before I can get to this..I have a long list of
tasks.. :))

On 2008-06-10 14:53:36 -0800, Jeff Ramsdale <jeff.ramsdale@gmail.com> said:

> Hi Miles,
>
> Thanks for your interest!
>
> This is the list of dependencies for the Ecore ODA driver itself (i.e.
> not the UI):
>
> org.eclipse.core.resources
> org.eclipse.core.runtime
> org.eclipse.datatools.connectivity.oda
> org.eclipse.datatools.connectivity.oda.design
> org.eclipse.datatools.connectivity.oda.profile
> org.eclipse.emf.ecore.xmi
> org.eclipse.emf.query.ocl
> org.eclipse.ocl.ecore
>
> These, of course, do have transitive dependencies.
>
> For the near term I don't see having the Ecore ODA Driver available on
> an update site. While we'd love to get there we have limited time to
> get to our backlog and that might be a big step. We're the first
> project in the DTP Incubator and there would need to be some
> infrastructure set up and coordination with the rest of the community.
> There's also the issue that we depend on EMF 2.3 and Java 5, which is a
> constraint the rest of the DTP family isn't subject to.
>
> We'd be interested in hearing about your experiences with the Driver
> (and recommendations/bug reports if you have them).
>
> -jeff
>
> Miles Parker wrote:
>>
>> Hi,
>>
>> Really excited about the ecore ODA driver, scratches a big itch. For my
>> usage, all of the setup will be done programmatically -- I'll be using
>> it as a front end for charting of live models. So for packaging
>> purposes I'm wondering what dependnecies the ODA driver alone will
>> have. That is, does it need the BIRT designer, EMF Transaction, DTP
>> JDBC, etc..? Basically, do you envision having a fully p2 capable
>> (whatever that might mean :)) update site that grabs what's needed?
>> Trying to avoid dependency trauma for my users..
Previous Topic:How to launch SQL Editor
Next Topic:How to launch SQL Editor
Goto Forum:
  


Current Time: Fri Dec 19 10:14:11 GMT 2014

Powered by FUDForum. Page generated in 0.13177 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software