Yeah, I could definitely be building it incorrectly. I think I got frustrated
with changes not going through and probably err on the side of wiping stuff out
(cleaning, rming target, etc) in order to just have one command (a bash script)
to deploy rather than having special commands depending on the type of change I
made. I added to DS-900 to cover this and DS-901 because that seems pretty
tightly intertwined. I would like to help as much as possible, but am still
not sure that I understand the build process well enough to write something up.
Let me know what I can do.
Thanks,
Alex Lemann
From: Mark Diggory [mailto:mdigg...@gmail.com] On Behalf Of Mark Diggory
Sent: Thursday, May 12, 2011 6:23 PM
To: Graham Triggs
Cc: Lemann, Alexander Bernard; Tim Donohue; DSpace Developers
Subject: Re: [Dspace-devel] Async releases discussion
On May 12, 2011, at 3:11 PM, Graham Triggs wrote:
On 12 May 2011 16:51, Lemann, Alexander Bernard
<ablem...@bsu.edu<mailto:ablem...@bsu.edu>> wrote:
I have had trouble with the *customization* documentation. How do I rebuild &
reinstall just my changes so things won't take ~3 minutes?
I just ran some compilation tests. From scratch - ie. no existing local Maven
repository - a complete build of dspace JARs and the assembly project took 8
minutes.
Cleaning the build directories, and then re-running the build for all projects
(but using the now populated local Maven repository) took 56 seconds.
As an aside... I'm curious what it would take if you removed the dspace-xxx
projects from the source/build and your local repository and just did the
dspace-release assembly process + download of the artifacts from the remote
repo, can you time that for us? I want to know how long the assembly process
for dspace-release.zip is when you don't have the maven repository "primed".
Cleaning and then rebuilding just the assembly / overlays took 36 seconds.
Admittedly, this is quite a fast machine. So one thing you can do to keep the
times down is upgrade! But, even without that, there are steps that you can
take to minimize the time taken.
If you are just making changes to configuration, JSP / XSL files, etc. and not
altering the supporting business logic, then you should probably only be
working with the assembly project and overlays. If you don't need some of the
web applications - like LNI, either of JSP or XMLUI, etc. then you should
remove those overlays from your assembly project.
G
Quite true
Mark
--
Mark R. Diggory
@mire - www.atmire.com<http://www.atmire.com>
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Technologielaan 9 - 3001 Heverlee - Belgium
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
