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
We use the git-commit-id-maven-plugin to generate the git.properties file. After a breaking change #699 of the time format in Version 8.0.0 the agent throws a DateTimeParseException for e.g. '2024-02-12T13:26:52+02:00' (see screenshot)
It would be very helpful if the agent also supported the new time format.
Best Uwe
The text was updated successfully, but these errors were encountered:
Thanks for taking the time to report the issue!
The agent already has an option artifactory-git-properties-commit-date-format that you can use to adjust the expected data format to e.g. yyyy-MM-dd'T'HH:mm:ssXXX. As this is the new default for the maven plugin we will be adjusting the agent to accept the new data format by default without additional configuration soon.
Sometimes, there are nice coincidences 🙂 I was just touching the code for a different feature and already improved the date parsing logic in non-Artifactory scenarios. So the fix was quite easy to carry over to the Artifactory use case 🥳
Hello CQSE Team,
We use the git-commit-id-maven-plugin to generate the git.properties file. After a breaking change #699 of the time format in Version 8.0.0 the agent throws a DateTimeParseException for e.g. '2024-02-12T13:26:52+02:00' (see screenshot)
It would be very helpful if the agent also supported the new time format.
Best Uwe
The text was updated successfully, but these errors were encountered: