On Mon, Aug 1, 2011 at 1:27 PM, Graham Triggs <[email protected]>wrote:
> Hi,
>
> On 1 August 2011 17:17, Tim Donohue <[email protected]> wrote:
>
>> 2. We need to make it clear how to install 'dspace-replicate' both to
>> command-line (copy JARs to [dspace]/lib/) and also how to install it to
>> XMLUI (copy JARs to [dspace]/webapps/xmlui/WEB-INF/lib/) and JSPUI, etc.
>> (And also make it clear that all these installs are separate -- you
>> cannot simply pull the JARs into a single location & expect it to be
>> fully installed throughout all of DSpace.) Is this "user friendly"
>> enough for a tool that is meant to make things more "user friendly" by
>> bringing more backup & restore functionality to Admin UI? Or are we
>> accidentally adding an unnecessary barrier here (by not having an
>> easy-to-install option, or having it already bundled out-of-the-box)?
>>
>
> Handily, I've just had a little bit of experience in this regards. Taking
> the 'binary' distribution (ie. the 'dspace' subdirectory of trunk):
>
> If you modifly the main pom.xml and add a dependency, that dependency (and
> it's dependencies) will be copied to the 'lib' directory of the assembly
> target (and in turn will ant update to your ${dspace.dir}/lib).
>
> If you modify modules/pom.xml and add a dependency, then it (and - you know
> the rest) will be copied to the 'WEB-INF/lib' of ALL of the modules (jspui,
> xmlui, sword, etc.) [this is because modules/pom.xml is a parent for all of
> the actual modules, so it inherents the dependencies].
>
> So, two pom.xml changes put the JARs into all of the correct locations -
> and those JARs are coming from a Maven repository (central, any others
> you've configured, or indeed your local cache if you've mvn install'ed
> them).
>
> G
>
I actually have a variant for the modules directory in one of the async
prototypes that looks like the following:
http://scm.dspace.org/svn/repo/dspace/branches/dspace-async-release/dspace/modules/
<http://scm.dspace.org/svn/repo/dspace/branches/dspace-async-release/dspace/modules/>This
reduces the changes to add a dependency to "all" modules to altering
dspace/modules/pom.xml and any alteration to add dependencies to "only" one
specific cli or webapp is done by adding it to just that one addon.
Mark
--
Mark R. Diggory
@mire - www.atmire.com
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Esperantolaan 4 - Heverlee 3001 - Belgium
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
