Actually, it reflects our need for improved overviews and published maven sites in this area. I'm hoping once the Confluence migration is finished we can begin to discuss a space in the WIKI and Manual for documenting the modules more extensively.
Mark On Mon, Mar 22, 2010 at 9:41 AM, TAYLOR Robin <[email protected]> wrote: > Didn't seem terse :) I had been wondering whether it was a deliberate policy > decision or just an inconsistency and you fully answered that. > > Cheers. > > Robin Taylor > Main Library > University of Edinburgh > Tel. 0131 6513808 > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Mark Diggory >> Sent: 22 March 2010 16:17 >> To: TAYLOR Robin >> Cc: [email protected] >> Subject: Re: [Dspace-devel] Dspace Services source code >> >> The source code is present in both the svn repository and the >> maven repository. Utilizing any IDE like Eclipse or IDEA will >> resolve the source in the maven repository when doing code >> inspection/analysis. >> >> Otherwise, if you review the Maven project poms for the >> service, you will find that the source is available in the >> scm repository >> here:http://scm.dspace.org/svn/repo/modules/dspace-services >> >> And will be managed under an independent JIRA project here: >> http://jira.dspace.org/jira/browse/DSRV >> >> Likewise, when you want to work on the code, you can just >> checkout the project in parallel to DSpace and add it as a >> Maven module to the build process, much like the other >> modules. This was the original intent with the modularity of >> those modules not to be maintained all on top of eachother. >> Otherwise there was no reason to start separating apart the >> codebase we did in 1.5 in the first place. >> >> The project, much like the i18n modules is a model for how we >> are trying to manage modularity in 2.0 and likewise addon >> module projects that are used in multiple version trees >> without releasing new versions that seldom change. The code >> originated from the DSpace 2.0 project and needs to be >> maintained for both targets. Likewise, in recent >> conversations with the Fedora folks we've seen interest in >> the possibility of using it there as well. >> >> It its important to recognize that the old monolithic source >> tree mode of maintaining a codebase needs to change for >> DSpace, we are just managing the compilation of way too much >> code in any release/install. >> The approach needs to change as the size of the team grows, >> the management of the codebase needs to become more >> distributed across separate modules that can be maintained >> independently. We need to finish the work that was started >> with the restructuring of the codebase in 1.5. >> >> Sorry, if this seems terse, We've worked pretty hard to make >> it possible to work with these project independently as >> modules. Its important that we not backside and start trying >> to shoehorn all the source code into one svn project again. >> If your looking at something that is an issue in the dspace >> services code, your welcome to address it in the DSpace >> Service JIRA project and make contributions to the SVN >> codebase there, we can even do another maven release (on a >> shorter timeline than even the 1.7 release) sot hat the >> contributions can be made available to users of the 1.6.0 tag. >> >> Mark >> >> >> On Mon, Mar 22, 2010 at 3:38 AM, TAYLOR Robin >> <[email protected]> wrote: >> > Hi, >> > >> > I was looking at the 1.6 source code distribution recently >> and trying to find my way through the Dspace Services stuff. >> I found it a frustration that the source code was not >> included. I was wondering if it would be possible to include >> it in future, or would that be a daft thing to do ? >> > >> > Cheers, Robin. >> > >> > >> > Robin Taylor >> > Main Library >> > University of Edinburgh >> > Tel. 0131 6513808 >> > -- >> > The University of Edinburgh is a charitable body, registered in >> > Scotland, with registration number SC005336. >> > >> > >> > >> ---------------------------------------------------------------------- >> > -------- Download Intel® Parallel Studio Eval Try the new >> > software tools for yourself. Speed compiling, find bugs >> proactively, >> > and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > Dspace-devel mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/dspace-devel >> > >> >> >> >> -- >> Mark R. Diggory >> Head of U.S. Operations - @mire >> >> http://www.atmire.com - Institutional Repository Solutions >> http://www.togather.eu - Before getting together, get t...@ther >> > -- > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > -- Mark R. Diggory Head of U.S. Operations - @mire http://www.atmire.com - Institutional Repository Solutions http://www.togather.eu - Before getting together, get t...@ther ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
