stefanseifert commented on pull request #13: URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/13#issuecomment-1064031216
i can confirm that this PR actually fixes the problem loading composum on my windows environment, same as https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/12 what is not so nice with this PR is the "log experience" - although nothing is "wrong" a lot of error messages are logged only due to the delayed startup behavior: [220310_error.log](https://github.com/apache/sling-org-apache-sling-jcr-contentloader/files/8223524/220310_error.log) such an error message is important if there is really no fitting content reader present. but it should not be shown only because the reader from the same bundle takes a few microseconds more to load to be ready. this is confusing for anyone monitoring the error log. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
