[
https://jira.duraspace.org/browse/DS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23891#comment-23891
]
Tim Donohue commented on DS-921:
--------------------------------
The DSpace Developers discussed this idea in our meeting on Jan 11, 2012.
Our main question was whether there is still a script/patch forthcoming? The
general idea is nice, but there's obviously several ways to achieve some of
these scenarios already with DSpace. One idea was to investigate Git/Github
(which is something the DSpace Developers are looking more closely at ourselves
for future DSpace development). Another is to look more closely at various
IDEs (IDEA, NetBeans or Eclipse) which often help one to more easily
build/deploy/test/analyze in a "one step process". IDEs also help out in patch
generation, code coverage, etc. rather than requiring one to write these tools
into a script. So, in general, we were interested in this idea, but we had
many questions around the script itself and whether it provides anything above
and beyond what is available to developers in IDEs.
A few resources that may be of interest:
* Various hints on using DSpace with major IDEs:
https://wiki.duraspace.org/display/DSPACE/Developer+Guidelines+and+Tools
* Initial thoughts on developing with DSpace in Git/Github:
https://wiki.duraspace.org/display/DSPACE/Tracking+your+source+code+with+Git
In any case, we look forward to seeing whatever script you post!
Here's the full discussion from yesterday's meeting:
[20:16] <tdonohue> moving along, next up: DS-921
https://jira.duraspace.org/browse/DS-921
[20:17] <richardrodgers> maybe ping reporter to see if he still intends to post
a new version?
[20:19] * mhwood tries to figure out how they managed to wind up under all
those constraints.
[20:19] * mhwood thinks maybe they want to look into Git.
[20:20] <mhwood> It sounds like three issues to me.
[20:20] <tdonohue> not very clear whether this build script uses Maven or not.
but, then again, I notice the build script itself wasn't posted for us to review
[20:21] <PeterDietz-alt> I just realized I'm very spoiled now that I have IDEA.
Press the green button to rebuild + start tomcat server, press the blue button
to rebuild/recompile + hotswap affected classes.
[20:22] * robint (52292725@gateway/web/freenode/ip.82.41.39.37) has joined
#duraspace
[20:22] <robint> Hi all
[20:23] <PeterDietz-alt> Edit trunk/dspace/pom.xml to set default.dspace.dir
default.dspace.password etc... and have each developer never commit that. They
all could use git and have own branches.
[20:23] <KevinVdV> Hi robint
[20:23] <tdonohue> it sounds like all we may be able to do here is ping
reporter (as richardrodgers suggests). Until we get the build script, it's hard
to tell for sure if there are other recommendations we can give (e.g. using
git, or using an IDE to help out with common tasks)
[20:24] <tdonohue> for Ds-921, I'll ping the reporter and ask about this script
-- assign tdonohue for now
> Build script supporting multi-developer config, automatic container launching
> and code coverage
> -----------------------------------------------------------------------------------------------
>
> Key: DS-921
> URL: https://jira.duraspace.org/browse/DS-921
> Project: DSpace
> Issue Type: New Feature
> Reporter: Gareth Waller
>
> The current DSpace configuration and build process makes modification
> difficult in a multiple developer environment e.g. a project with a couple of
> engineers.
> Consider the following scenario:
> - A project wishes to make significant modifications to the DSpace codebase
> - The project consists of multiple developers (potentially on different OS's
> and varying install paths for binaries e.g. maven)
> - Each developer wants their DSpace to be stored in potentially a different
> location to another developer e.g. their home dir
> - Each developer wanted a one step process to build, deploy and launch DSpace
> within a container (to make development and testing quicker)
> - Code coverage analysis was required to see how effective system tests were
> - The project doesn't want to commit their entire DSpace codebase to their
> own internal source code management system e.g. svn
> - The project needs to know exactly at any point in time which DSpace files
> were modified (and what those modifications were)
> - An easy way to generate a patch is required in order to raise a Jira and
> submit the code back to DSpace
> - An easy way to perform automated web testing was required for a nightly
> build
> The scenario described above was encountered on the UK Jorum project and we
> created a build script to facilitate the above.
> See http://developer.edina.ac.uk/projects/jorumdspace/wiki/Build_Framework
> The build script used in the Jorum project might be a useful AddOn to DSpace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
