[
https://jira.duraspace.org/browse/DS-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22930#comment-22930
]
Brian Freels-Stendel commented on DS-1060:
------------------------------------------
Well, as I say, I don't use that option, myself, but my suspicions tend this
way.
If I run ant -Dconfig=[path/to/config/dspace.cfg] update, I would have the
intent that the specified config file is the one I'm going to be using in
production, while I may not have updated the source config for some time. I
think (and this is where I often diverge from the rest of the world) that, in
the case of upgrading to a new version, I would have prepared the specified
file for that upgrade. (If not, there's a fair chance something may not work
right anyway.) Additionally, deploying with one config and then using another
to actually run the app seems like it might introduce another avenue for odd
things to crop up.
It seems logical to me (and, again, I may not be on the same page as others)
that if no -Dconfig is specified, the source file should be used; if it _is_
specified, the specified file should be the one that ends up as the deployed
file.
It's kind of like the overlay mechanism in my mind, with the existence of the
-Dconfig option being the catalyst.
It's certain, though, that I have less experience with this sort of thing than
any of the developers, much less all of them. If no one else pipes up, I'd
lean toward going with that experience.
> 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
