[ 
https://jira.duraspace.org/browse/DS-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22933#comment-22933
 ] 

Mark H. Wood commented on DS-1060:
----------------------------------

Unless I misunderstand something, it seems to me that #1 and #2 should both 
copy the config which ant uses to the target directory.  Otherwise you have (in 
#2) exactly the unwanted behavior:  ant uses one configuration to install and 
then DSpace runs off another.  Comment 3 seems to say that ant update 
-Dconfig=blah should NOT copy the config to the target.  ???

I too expect to first produce a dspace.cfg starting with the upgrade version's 
stock text and substituting the values I require, and to use that to both 
install and run DSpace.  One can customize the .cfg in the [DSpace-source] 
directory but I don't.  One can build the customized .cfg in [DSpace]/config, 
which is what I do in a production environment.  One can build customized .cfg 
files somewhere else and let ant update copy it to [DSpace]/config, which is 
what I do in my test environment where I have a lot of related config.s all in 
one directory for easy borrowing.  I would expect all three of these to do the 
Right Thing:  an undamaged copy of the configuration used by ant winds up in 
[DSpace]/config.  When that's where it already is, ideally we would do nothing, 
but it would be acceptable to copy the file over itself if this can be done 
without damage.
                
> When running 'ant update' copy dspace.cfg to *.old in line with all the other 
> config files
> ------------------------------------------------------------------------------------------
>
>                 Key: DS-1060
>                 URL: https://jira.duraspace.org/browse/DS-1060
>             Project: DSpace
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>            Reporter: Robin Taylor
>             Fix For: 1.8.0
>
>
> Ant target overwrite_configs contains the following line...
> <globmapper from="*" to="*-${build.date}.old" />
> Whereas target prepare_configs contains the following line...
> <globmapper from="*" to="*.default" />
> It may be just a case of bringing prepare_configs in line with 
> overwrite_configs but I haven't had a chance to analyse this properly.

--
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

        

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to