Hi Susan, I hate to revive a really old email thread, but I was wondering if you've even been able to successfully module overlay your dspace-api changes? http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg06770.html
<http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg06770.html>Anyways, in preparation of upgrading, I've been refactoring all of our changes, and putting all of our work into [src]/dspace/modules/... and I was having a really hard time getting changes made in modules/custom-api actually applying. Thats when Googling around brought me to the old email thread. Anyways, since I've been able to talk with (more so much prod) Mark Diggory, Tim Donohue, and Kim Shepherd on IRC, I've finally been able to get custom-api changes to actually work. Based on the email thread, it looked like you were able to get custom-api to get its jar to go to /dspace/lib/custom-api.jar next to /dspace/lib/dspace-api.jar, however the changes you've made never really applied to anything. Atleast that was my problem. To get it to actually apply, you have to add your custom-api as a dependency to the webapp that you are using, as custom-api.jar needs to be used by the webapp. Who's jars live in /dspace/webapps/jspui/WEB-INF/lib/ The trick that did it for me, was to add to [src]/dspace/modules/jspui/pom.xml <dependency> <groupId>org.dspace.modules</groupId> <artifactId>custom-api</artifactId> <version>${project.version}</version> </dependency> And rebuild. If this is old news and you've solved it, then good, otherwise, hopefully someone will stumble upon this and find it useful. I'll also be adding a note to confluence if this part hasn't been clear. (Its clearer now that its working ;) ) Peter Dietz Systems Developer/Engineer Ohio State University Libraries
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
