Title: Message Title
|
|
|
|
This does sound like a possible good addition to build.properties.
However, without an immediate volunteer, this may need to wait for 5.0 (as it's a config change). The 4.0 release is hopefully "wrapping up" in the next few days, so it'd need to be committed before the end of the week.
It is worth noting that anyone can manually tweak which settings they want available in their build.properties. For this scenario, I believe all you'd need to do is create a new config (e.g. "dspace.url") in build.properties, and then tweak your dspace.cfg to have:
dspace.url = ""
This same idea holds true for all configuration files (dspace.cfg or any config under [dspace]/config/modules/). It's possible to move *any* configuration to build.properties and then modify the corresponding config file to just reference that new build.properties setting via: "${name-of-config-in-build.properties}"
|
|
|
|
|
|
|
If we want people to see build.properties as the most basic set of config params to look at and evaluate, I think the choice of "primary" UI should be in there as well.
Currently, dspace.url is defined in dspace.cfg as:
dspace.url = ""
Which actually means that if you want to use JSPUI, you should also go to dspace.cfg after ...
|
|
|
|
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
