This has been brought up before. There used to be a way to do it in OH 1.x but they have since changed how config files are loaded and that approach is no longer valid.
There is still no way I know of to force the order of loading the files.
I’m going to recommend looking at the ESH Issues to see if there is already one open for this and if not, create one. It doesn’t seem to be a problem on people running on less powerful machines but those of us running on faster machines it does cause problems.
BTW, to get rid of the toDateMidnight deprecation warnings use withTimeAtStartOfDay instead. It does the same thing. I’ve no idea whay Joda changed it. I like the old method name better.
I think the “There is no context to infer the closure’s argument types from.” warning is referencing a lambda. Try using the defintion style I use here in the Updated Syntax section. This lets you specify the Types of the arguments and return value of your lambda and I think this warning will go away.
Some other less than satisfactory approaches you can use to deal with the warnings and error messages:
- shunt the Sitemap logs to a separate file. Out of site, out of mind. I do this with zwave because it is so chatty in the logs.
- set a flag in a System started rule and use that flag to prevent or delay execution of the rest of your rules until such time you are confident the .items files are fully loaded.