Thanks alot Peter that would be useful.
My research is going to be about the search interface of Dspace so any tips you
could give me on how to edit that as well would also be very useful.
Thanks
Craig
From: [email protected]
Date: Tue, 16 Nov 2010 17:47:42 -0500
Subject: Re: [Dspace-tech] setting up development environment
To: [email protected]
CC: [email protected]
Hi Craig,
There's no reason for the documentation to be unfriendly for those first
getting started, its just that once you've gotten familiar with DSpace, you
don't look at the getting started docs anymore, thus, they might go
unmaintained. If I have time, I might put up a tutorial to get your feet wet
with getting started.
Comments are in line.
--
Peter Dietz
Systems Developer/Engineer
Ohio State University Libraries
On Sat, Nov 13, 2010 at 12:04 PM, Craig Brute <[email protected]>
wrote:
Hi,
I am looking to do some dspace development as part of a university project but
am having some trouble understanding certain parts as this is the first time i
have worked on a project of this size.
i have been following the instructions for Building DSpace From Source
(https://wiki.duraspace.org/display/DSPACE/Building+DSpace+From+Source) i have
managed to install and get dspace running from the dspace system documentation.
I am running windows 7 with tomcat and am unsure how to edit the following code
to produce a batch file to use when i am developing. An explaination of each
line of code and what it does would be hugely appreciated
First some terminology:
[dspace-source] or [dspace-src] == The downloaded (from zip or svn) source code
for dspace. Contains a pom.xml and folders like dspace, dspace-api,
dspace-jspui, dspace-xmlui, and more. If you are making changes to java files,
you'll make those changes to these files. This might be located on your
computer somewhere like /home/dspace/dspace-source or C:/dspace-source
[dspace] == The "binary" dspace that is executed by java or tomcat. You create
this file either by downloading a binary release of dspace that comes
precompiled, or you compile the source directory and use a tool to copy the
compiled files to this location. This contains folders like assetstore, config,
logs, webapps. This is typically located somewhere like /dspace/ or C:/dspace
Hopefully this makes sense:
$CATALINA_HOME/bin/shutdown.sh
Shuts down Tomcat (the web server). If you have a GUI for managing tomcat, then
just stop tomcat.
cd /path/to/your/src/dspace
Go to your dspace source code, [dspace-source]. You can change this to
something like: cd C:/dspace-source/dspace
mvn package
Compile the source code into machine code. The reason for mvn/maven is to
minimize the overall complexity, we can fetch 3rd party code that does things
like extracting text from PDF's from the internet. DSpace doesn't have to ship
the dependency, but maven can figure out dependencies.
cd target/dspace-1.5-SNAPSHOT.dir
The previous step created a "target" folder where it put all the compiled
output files. So change directory to it.
ant -Dconfig=/dspace/config/dspace.cfg update
This copies all the compiled files and to your running [dspace] directory.
-Dconfig=/dspace/config/dspace.cfg means that you want to preserve the existing
dspace.cfg you had before that resided in [dspace]/config/dspace.cfg when its
copying or overwriting files.
rm -r $CATALINA_HOME/webapps/dspace-*
cp -r /dspace/webapps/* $CATALINA_HOME/webapps/
These steps might not be necessary depending on how you have tomcat configured.
Personally I have tomcat serve webapps from [dspace]/webapps, so this step is
unneeded for me.
So, your servlet container, aka webserver for java files, has a default
location that it will serve webapps from. This would remove anything you had
there before, and then copy the newly recompiled webapps there. I find not
having to do this step beneficial.
$CATALINA_HOME/bin/startup.sh
Start tomcat back up.
Also is it absolutely neccessary to check dspace out from the SVN if i
previously downloaded the source code from source forge?
They're identical. So this doesn't matter. It is recommended that you do your
custom development in some sort of source-code-version-control system. So as
you make progress on changes / features, you keep progress of changes. There
might not be good guides for how to do this with dspace setup, but you'll want
to make your own svn, git repo to manage this.
Thanks for any help you can provide.
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
