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
In the above example the data.expirations property does not exist in the object data. e.g. getExpiration() is valid. But the method/property .getExpirations() does not exist and should fail the build. We're looking for a way to ensure the build fails if there's such a typo.
After updating to the latest 3.x version of jspc-maven-plugin we're finding that a build with the above error still succeeds.
The text was updated successfully, but these errors were encountered:
Thanks. I did try version 4.1.0 and unfortunately it didn't catch the
invalid property. We're likewise looking to move away from JSP towards
Thymeleaf and other view technologies but still have a lot of legacy JSP
On Fri, Feb 10, 2023 at 4:33 AM Leonard Ehrenfried ***@***.***> wrote:
Have you tried with the latest version 4.1.0.
I must admit that I haven't touched JSPs in over ten years so I have no
idea if that is according to the spec or not.
I'm not going to investigate this problem but if you have a PR that fixes
it, I'm happy to merge it in.
—
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJDHBZJWIHWDIIBQRCWQR3WWYDORANCNFSM6AAAAAAUXCJZOQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
I would expect the jspc compile to catch the following invalid property error and cause the compile goal to fail
In the above example the data.expirations property does not exist in the object data. e.g. getExpiration() is valid. But the method/property .getExpirations() does not exist and should fail the build. We're looking for a way to ensure the build fails if there's such a typo.
After updating to the latest 3.x version of jspc-maven-plugin we're finding that a build with the above error still succeeds.
The text was updated successfully, but these errors were encountered: