|
||||||||
|
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 |
||||||||
------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
1) We could add a script to DSpace that create a directory containing everything needed to run an external handle server.
2) We let maven and ant build this directory.
3) We just document how to build the directory yourself.
In all cases we can add the ExternalHandlePlugin into the handle-<ver>.jar at the central repository that already gets maintained by DSpace and not by CNRI, we can use maven to produce a jar that contains the ExternalHandlePlugin only or we just use dspace-api-...jar which already contains the ExternalHandlePlugin and contains a lot of other stuff that an external handle server don't need.
I would prefer to add the ExternalHandlePlugin to the handle-<ver>.jar as I think its an easy solution and this jar is maintained by DSpace already. But I can totally live with any other solution. What do you think?