[dtp-dev] Request to remove emf-sdo dependency

[David M Williams <david_williams@xxxxxxxxxx>]

We are looking for ways to remove/reduce
some of our dependancies in WTP
(in our whole "stack" of dependancies,
not literally just WTP).

One of those is the emf-sdo plugin.


I've opened a bugzilla to track the
issue, 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=208455
but thought I'd repeat it here
on these lists to be sure a wide audience
is aware of the issue, and can
voice concerns or known problems ...
in case there's any small subtle
issues that are not obvious from the
compile time or manifest
dependancies.

So, please comment in the bug if there
are issues or concerns, but I'll
repeat it here for convenience.

= = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=208455

In an effort to "cleanup"
and reduce our dependency stack in WTP, one item
that appears to be low hanging fruit
is the emf-sdo plugin, from the EMF
Project.

But, it appears that we (JPA) have an
indirect need for it, via the DTP
project code (I think though some connectivity
code? if not elsewhere?).

Especially since there are now new SDO
Spec Releases (a version 2, as
implemented by an Apache Project called
Tuscany) and, I hear in my virtual
hallways, some other potential SDO implementations
in some other Eclipse
persistence frameworks, then I suspect
it's time to move off the "old" EMF
SDO plugin.

I'd like to request the DTP teams to
see if this is feasible to include
this removal in this Ganymede release?
And if so, probably the earlier the
better! (to avoid last minute discoveries
of issues). Would M4 be
feasible?