You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using the timestamp property (see below for complete configuration), then for some months the result is corrupt. For example, at the moment the German month is called "März" (march), the result then with the plugin is "26.März.2024 18:01". As you see the plugin is has problem to write the special character in the month name properly. This is the plugin configuration:
Hi, we are using windows 10 as development environment, we have actually a utf-8 development environment.
See attachment how the result is generated when I access the build date:
The German Name of the month is "März" but the german Character "ä" is generated wrong, although it is an UTF-8 JSP page. The problem ist, that the maven plugin saves/writes this date already internaly wrong.
I have updated to initial comment so that you see all the important parts of the plugin usage/conf. We don't do anything special except then after running a web application accessing the date / time that the maven plugin has set and representing it in website. But before the website get the value to show it is already saved with wrong character. So it is not because the JSP can not show it but because it was generated wrong into the property "build.time" .
Hallo,
when using the timestamp property (see below for complete configuration), then for some months the result is corrupt. For example, at the moment the German month is called "März" (march), the result then with the plugin is "26.März.2024 18:01". As you see the plugin is has problem to write the special character in the month name properly. This is the plugin configuration:
We use this plugin in version "1.4" but I also has changed it to the newest version 3.2.0 but it was the same problem.
Can you make a bugfix please?
Thank you very much and God bless you!
The text was updated successfully, but these errors were encountered: