On Mon, Oct 29, 2012 at 12:59:29PM +0000, João Melo wrote: > As DSpace grows, the number of modules grows. However, DSpace already has > lot's of modules (there are also some planned contributions that will > increase this number) and, in the general case, some of them aren't used at > all. Also the current add-on deployment procedure is complex, most of the > add-ons requires a DSpace rebuild and re-deployment (restarting the webapp > container), this complexity grows if one tries to apply multiple add-ons.
I have often wondered how many add-ons really need to be built *with* DSpace rather than *against* DSpace. I've done a couple of small local add-ons which are built entirely separately, name necessary DSpace artifacts as dependencies, produce their own JARs, and can be added by dropping the JAR into [dspace]/lib and adding a little configuration. It should be possible to do something like that with any code that doesn't alter or replace stock classes. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgp7kzqYeQLH6.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
