Mark W, Thanks for getting down to the heart of the issue/question.
I agree completely, that we should officially vote on our commitment to DSpace Services, and officially mark all classes that will be replaced with @deprecated notes. I've added a note about this to today's DSpace Developer Meeting agenda. I cannot guarantee we'll get to it today (as we have a lot of topics already), but I'll make sure to carry it over to next week's agenda as necessary. https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-03-30 Personally, I feel we should commit to Services Framework for all new code additions, and deprecating the older ways of doing things. However, I'd like to also hear any concerns others may have around going this route, and whether there are ways to alleviate those concerns. For instance, is there a way we can bring Services more "into the light", rather than being in the "shadows", as Mark W puts it. https://wiki.duraspace.org/display/DSDOC/DSpace+Services+Framework So, if anyone has concerns/questions to pose around the Services Framework, please feel free to do so in this email thread. To get this issue behind us, I'd like to call for an official 'vote' on deprecating older classes in very near future (likely in our meeting next week, April 6, if we can fit it in). So, I ask that we please try to discuss any concerns/questions via email, if possible. - Tim On 3/30/2011 9:03 AM, Mark H. Wood wrote: > There are several things going on here. > > o The dark side of greater modularity and Maven's magical > behind-your-back dependency management is that we lose sight of > some of the pieces. The Services Framework and core services have > been In There for some time but we never notice them; "DSpace" is > whatever you get when you check out svn/repo/dspace/trunk, plus > some shadowy stuff that Maven takes care of (which now includes > Services and will surely grow to encompass other parts of the > product). > > o I don't believe there has ever been a completed call for consensus > on Services. The developer community as a whole have not signed up > to the notion that this is the way forward. Without a group > commitment, inertia will rule and Services will languish. We've > talked about it quite a lot but the talk has never advanced to a > decision. > > We need to reach that decision and, assuming "yes", mark the > ConfigurationManager and PluginManager as @deprecated so we're > constantly reminded, "oh, yes, I should use the Whatsit Service now." > If there are reservations then let's get them on the schedule and > address them. We need to get beyond this point, one way or the other. > > > > > ------------------------------------------------------------------------------ > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and > publish your website. http://p.sf.net/sfu/ms-webmatrix-sf > > > > _______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
