Sorry about the delay ... I finally just got subscribed to the mailing list.
The Tuscany SDO implementation (SDO 2) is still dependant on EMF, but a different version than the SDO 1 implementation that the rest of Tuscany is currently using. Here is the history, and as close to a "plan" that we have so far. 1) The EMF-based SDO 1 reference implementation at Eclipse (which is currently being used by the rest of Tuscany) will be deprecated and replaced by the new SDO implementation here at Apache. 2) The initial SDO codebase in Tuscany is the result of a 6 week effort to put together a cleaned up and restructured version of the SDO 1 code from Eclipse, but with a clean separation from EMF. The goal was/is to produce a complete implementation of SDO 2 (in the Tuscany project) but use EMF as a hidden implementation framework. 3) Now, the EMF dependency is only from the SDO 2 implementation - as opposed to clients of SDO 2 or any other parts of Tuscany. The plan is to not make any EMF APIs available to clients - so the option of removing the EMF dependency in the future will be an SDO 2 only decision. Part of the restructuring also included some restructuring of EMF itself (at Eclipse) to make it more easily useable outside of Eclipse. For example, the EMF code generator, which used to require the Eclipse workbench (headless for command line generator), has been restructured to run completely standalone. As a result, the SDO 2 static code generator - which is just a customized invocation of the EMF generator - requires only two EMF jar files (emf-codegen.jar and emf-codegen.ecore.jar) as opposed to the whole Eclipse workbench. So, the short answer to your question is that the SDO implementation at Tuscany will have a dependency on a few EMF jars for the foreseeable future, but depending on the will of the community they may be removed/replaced at some point in the future. I hope this helps clarify things. Frank. Jim Marino <[EMAIL PROTECTED]> wrote on Tue, 3 Jan: > My understanding was that the Tuscany SDO implementation would not > have EMF/Eclipse dependencies. Is that not the case? > > Jim > > > On Jan 2, 2006, at 6:55 AM, Fuhwei Lwo wrote: > > > Two problems - > > > > The uploaded version of EMF under > > http://www.ibiblio.org/maven2/org/eclipse/emf/ is 2.1 not 2.2. SDO 2 > > requires EMF 2.2. > > > > Also, although SDO 2 is currently dependent on EMF 2.2, it only > > depends on > > 7 Jar files. > > > > emf/codegen > > emf/codegen-ecore > > emf/common > > emf/ecore > > emf/ecore-change > > emf/ecore-xmi > > xsd/xsd > > > > There are too many EMF files uploaded. > > > > Fuhwei Lwo > > > > > > > > > > Geir Magnusson Jr <[EMAIL PROTECTED]> > > 12/31/2005 12:42 PM > > Please respond to > > tuscany-dev > > > > > > To > > [email protected] > > cc > > > > Subject > > Re: Eclipse dependencies > > > > > > > > > > > > > > cool - thx > > > > Jim Marino wrote: > > > >> My understanding is that the SDO implementation that is being used by > >> the Java runtime requires EMF. That implementation is in the > >> process of > >> > > > > > >> being replaced so hopefully the need for the dependencies will go > >> away > >> > > :-) > > > >> > >> Jim > >> > >> > >> On Dec 30, 2005, at 1:32 PM, Geir Magnusson Jr. wrote: > >> > >> > >>> why are there so many eclipse dependencies? > >>> > >>> On Dec 30, 2005, at 6:08 AM, Guillaume Nodet wrote: > >>> > >>> > >>> > >>>> FYI, i asked the maven team to upload all needed eclipse > >>>> dependencies on ibiblio. > >>>> > >>>> See http://www.ibiblio.org/maven2/org/eclipse/ > >>>> > >>>> Cheers, > >>>> Guillaume Nodet > >>>> > >>>> > >>>> > >>> > >>> -- > >>> Geir Magnusson Jr +1-203-665-6437 > >>> [EMAIL PROTECTED] > >>> > >>> > >>> > >> > >> > >> > > > > > >
