Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

500 error when trying to add 3.0.x generation to Spring REST Docs' support page #1073

Open
wilkinsona opened this issue Jul 19, 2022 · 0 comments

Comments

@wilkinsona
Copy link
Contributor

Looking in the web inspector, the following content is being POSTed:

id: spring-restdocs
_generations[0].toDelete: on
generations[0].name: 2.0.x
generations[0].initialReleaseDate: 2017-11-28
generations[0].ossSupportEnforcedEndDate: 2022-11-17
generations[0].commercialSupportEnforcedEndDate: 2024-03-17
_generations[1].toDelete: on
generations[1].name: 1.2.x
generations[1].initialReleaseDate: 2017-04-24
generations[1].ossSupportEnforcedEndDate
generations[1].commercialSupportEnforcedEndDate
newGeneration.name: 3.0.x
newGeneration.initialReleaseDate: 2022-11-21
newGeneration.ossSupportEnforcedEndDate
newGeneration.commercialSupportEnforcedEndDate

Trevor's checked the logs and it's failing like this:

022-07-18 12:17:42.507 ERROR 16 --- [io-8080-exec-18] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.IllegalArgumentException: enforcedEndOfOssSupportDate should be after nextGenReleaseDate] with root cause

It looks like the problem is ossSupportEnforcedEndDate: 2022-11-17 combined with ossSupportEnforcedEndDate: 2022-11-17. Could this be caught on the client side?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant