Hi everyone, just to refresh your minds about the limitations here - you can't just declare _any_ property in your local build.properties. You can only fill in the values properties that are already there. In addition, you can't remove those properties that are there, either. Instead of removing it, you have to leave the right-hand side of the assignment empty. Therefore, we don't want to just keep adding stuff into build.properties - that way we would create another copy of all configuration files in one file :(
Now, it's unfortunate that these limitations exist and it was very predictable that it would come to these discussions about adding more properties into build.properties. Therefore it's very important to first decide what our definition of build.properties is (or view, as Tim calls it). My personal take on DS-1494 is that we do not want to add just search.user and search.password to build.properties. These properties are not usable by themselves, they require other LDAP options to work. If we included all (or most) LDAP options, we should also include properties for all other auth methods. I don't think that would fit either of those definitions Tim mentioned. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
