Skip to content
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

Fix for #204 #210

Merged
merged 3 commits into from Jul 12, 2015
Merged

Fix for #204 #210

merged 3 commits into from Jul 12, 2015

Conversation

TheSnoozer
Copy link
Collaborator

As described in #204 added the ability to set the timezone along with dateFormat.

I hopefully made it crystal clear in the docs that setting the timeZone in the plugin's configuration will override any other configuration.
The reason for this, is that we can not determine at which level the user has altered the timezone of java or the system. It could be in some configuration file or by setting runtime environment parameters like -Duser.timezone=UTC. If we investigate the system properties of java, we only see the latest version that was set. At this moment java does not simply ship an option to determine where the timezone was altered. Also I didn't want to introduce some garbage code that invokes a process builder that asks for the real timezone (or some other magic code that is system dependant).

@TheSnoozer TheSnoozer added this to the 2.2.0 milestone Jul 12, 2015
TheSnoozer pushed a commit that referenced this pull request Jul 12, 2015
Fix for #204: added the ability to set the timezone along with dateFormat
@TheSnoozer TheSnoozer merged commit f7b1671 into git-commit-id:master Jul 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant