|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Before I create a pull request I want to discuss the following:
As part of the development I created org.dspace.handle.ExternalHandlePlugin to connect from a handle server back to DSpace. It does not depend on any part of DSpace. Beside it you need three jars, one property file, a start script and the handle config (created by [dspace-bin]/dspace make-handle-config <dir>) to run an handle server. The easy way to pack this is to use the hole dspace-api...jar, but that seems a little bit bloated to me. The java handle client library in maven central repository (handle-6.2.jar) is maintained by DSpace. Is it possible to add a compiled version of the ExternalHandlePlugin into it? That would make the packaging of an external handle server much easier.