Hi Mathias, For options 2 and 3 make use of the <dspace-source>/dspace/modules directories. Put any new or modified classes in there and rebuild using maven. Its sort of the equivelant of the old jsp/local directory but not just for jsp's.
Cheers, Robin. -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathias Hjelt Sent: 29 April 2008 05:14 To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] FW: Creating add-ons or modifications in 1.5 Hello, I'd still appreciate some comments on this from the DSpace gurus out there.. I can't be the only one left wondering about how to best utilize maven for managing different types of DSpace customizations? Best regards Mathias Hjelt ---Original Mesage--- From: Mathias Hjelt [mailto:[EMAIL PROTECTED] Sent: 23. huhtikuuta 2008 9:20 To: 'dspace-tech@lists.sourceforge.net' Subject: Creating add-ons or modifications in 1.5 Hello, Ive been trying to get a grasp of how to port our own add-ons and customizations made in 1.4.2 to the brave new maven-based world of 1.5. I read the SimpleAddonMechanism on the wiki, but that document is still sort of under construction and didnt make things much clearer. Could someone with a better understanding of the maven build process suggest the proper best practice development approaches for the following three scenarios: Scenario 1: Creating a stand-alone Java application which uses the DSpace API. For instance a maintenance application which is to be run using dsrun, i.e. having the dspace classes on the classpath. Currently Ive been developing and building such apps in Eclipse with the entire 1.4.2 project source included, then copying the resulting custom class or jar file manually to [dspace]/custom from where Ive been running them with dsrun. Scenario 2: Creating a custom class that should be compiled into the webapp. For instance a custom plugin for the authentication stack. Currently Ive developed these classes with Eclipse, then added the custom source files into the base [dspace-source] and built the webapp normally using ant. Scenario 3: Making changes to an existing DSpace class. Suppose ones local installation needs a few hacks in an existing Servlet class. To accomplish this in prior versions, Ive applied our local modifications to the existing DSpace source files in [dspace-source] and then built as normally. Any help on how to accomplish the above three scenarios using maven practices is greatly appreciated! Best regards Mathias Hjelt ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao ne _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
