[
https://jira.duraspace.org/browse/DS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23921#comment-23921
]
Gareth Waller commented on DS-921:
----------------------------------
Its probably also worth saying:
- The directory 'filesToFilter' contains sym links to files which have values
which should be interpolated via Ant e.g. the dspace.cfg
- The directory 'filteredForCopy' contains sym links for files which should be
copied in a post build step. Note the directory structure indicates where the
file should be copied to under 'patched_src'. E.g. under filteredForCopy I
could have
dspace-xmlui/dspace-xmlui-webapp/target/dspace-xmlui-webapp-1.5.2/i18n/messages.xml
where messages.xml is a sym link to
../../../../../../build/filtered/messages.xml (i.e. the messages.xml which was
interpolated and stored under the build dir).
> 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
> Attachments: dspace_buildframework_180112.tar.gz
>
>
> 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
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
