Default properties should be stored visible in the Spark bin directory
Spark.properties etc are not stored the Spark installation folder. Hence default settings have to be part of the code. It would be better to have these settings in files that are copied from the installation folder to the profile folder. New users of Spark on that PC installation will have the default settings via a copy of the "default.properties". For a corporate environment, this methods is prefered, as it a allows a customization of default settings without recompiling Spark
(This assumes that a corporate environment has the capability to repackage an installation into a new installer)
Mass closing of all bugs resoved during 2.6.0 and 2.6.1
There are several options to do this. The best would be an Openfire Plugin, that controls the file Spark properties. This is too much in the current state of the development capacities at hand. The default settings are currently in jar file. I was in favor of pulling them out of the jar into a text file. This would expose the settings pretty clearly to the end user and manipulations via Notepad. Wolf an I decided to leave them in a jar. This is security by obscurity, but it is the lowest effort.
Maybe we should discuss the need for the Spark Client control plugin on OF and Spark side. But I would assume that the development effort for a good implementation is several weeks.
Well, in a corporate environment it would be easier to have a separate config file (which shouldn't be overwritten while updating the program) for doing updates. Because now one have to push an upgrade and then customize and push new spark.jar
discussed with walter.
it can be accessed within the spark.jar at: spark.jar\org\jivesoftware\resource\default.properties
thats visible enough