-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
detectChange causes an erroneous log message in dev modeon Play start #1008
Milestone
Comments
xael-fry
referenced
this issue
Oct 14, 2016
xael-fry
added a commit
to xael-fry/play
that referenced
this issue
Oct 19, 2016
…ed configLastModified on application start
xael-fry
added a commit
to xael-fry/play
that referenced
this issue
Oct 20, 2016
…ed configLastModified on application start
xael-fry
added a commit
that referenced
this issue
Oct 21, 2016
[#1008] fix(ConfigurationChangeWatcherPlugin): initialized configLastModified on application start
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Report by @selangley 1a0f924#commitcomment-19419445
This causes an erroneous log message in dev mode:
ERROR play - Restart: Need to restart Play because \application.conf has been changed
because when detectChange() is first executed the value of long configLastModified has not been properly initialized yet. It's value is 0. So the ConfigurationChangeWatcherPlugin will think a change has occurred to the application.conf when it it fact has not occurred. The value of configLastModified only gets initialized later when onConfigurationRead() is called.
Here is a snippet from my log file showing the order in which these methods were called:
The text was updated successfully, but these errors were encountered: