Yes, again! Just some ideas: o See if there is some way to push the testing framework out of dspace-api so it can be shared across projects without causing dependency tangles. Of course tests themselves remain with what they test.
o Put source-build and binary distributions on the same level. Either make the binary a separate top-level project, or create dspace-source-build and dspace-binary-build projects under parent. (Extra points if someone figures out a way to get Maven to complain "change to dspace-source-build or dspace-binary-build and try again", if the latter.) dspace/modules/ moves with the rest of the binary build. o Split up [dspace-source]/dspace/. Most of this stuff gets distributed to the project(s) that it is for. Continue breaking up dspace.cfg and part out the fragments to the projects they configure. Final assembly will stitch all the pieces together. dspace/docs/ moves up. Discussion? -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgp5Sw2Syh8kb.pgp
Description: PGP signature
------------------------------------------------------------------------------ The Windows 8 Center In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
