You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@grails.apache.org by "J. Jason, DJ - FM/AM" <JJ...@proton.me> on 2026/09/22 15:38:07 UTC
Grails 7 migration question: Javax vs Jakarta on error page?
The /views/error.gsp page generated by the Grails Forge still references javax.servlet.error.exception -- should that be jakarta.servlet.error.exception, or am I missing something about the javax => jakarta migration?
[Screenshot 2026-09-22 at 10.13.36 AM.png]
FWIW, both packages are mentioned together in https://github.com/jakartaee/servlet/issues/388, suggesting they are equivalent-ish...but I'm very new to this, so I could easily be mistaken.
Re: Grails 7 migration question: Javax vs Jakarta on error page?
Posted by Mattias Reichel <ma...@apache.org>.
Hi Jason, good catch on the Quartz plugin, that version should be
removed: https://github.com/apache/grails-core/pull/16395
The web console version is to my knowledge not managed by the Grails
bom and should stay.
Thanks
Mattias
Den tors 24 sep. 2026 kl 17:56 skrev J. Jason, DJ - FM/AM via users
<us...@grails.apache.org>:
>
> Thanks for the speedy fix, Søren!
>
> Another Grails Forge discrepancy, one that doesn't seem worth a new thread (let me know if that would have been better!) -- some of the Additional Selected Features seem to not have been updated as part of deprecating per-dependency versions:
>
> The Upgrading the Quartz Plugin section of the Grails 7.2.3 upgrade docs says about that plugin that "The version is now managed by the Grails BOM, so it should be removed from the dependency declaration" -- yet the generated build.gradle file (when adding the Quartz Feature) shows that dependency with a version:
>
> implementation "org.apache.grails:grails-quartz:4.0.0"
>
>
> If there's a reason that version is needed, a comment explaining why would be helpful -- or, if not, removing the version seems wise
>
> The Web Console Feature also includes a version -- though its coordinates suggest it may not be managed by the Grails BOM, so perhaps it is needed in this case (again, if so, an explanatory comment would be helpful):
>
> runtimeOnly "org.grails.plugins:grails-web-console:7.0.0"
>
>
> Thanks for clarifying these minor questions!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@grails.apache.org
For additional commands, e-mail: users-help@grails.apache.org
Re: Grails 7 migration question: Javax vs Jakarta on error page?
Posted by "J. Jason, DJ - FM/AM via users" <us...@grails.apache.org>.
Thanks for the speedy fix, Søren!
Another Grails Forge discrepancy, one that doesn't seem worth a new thread (let me know if that would have been better!) -- some of the Additional Selected Features seem to not have been updated as part of deprecating per-dependency versions:
The [Upgrading the Quartz Plugin](https://grails.apache.org/docs/7.2.3/guide/upgrading.html#_16_upgrading_the_quartz_plugin) section of the Grails 7.2.3 upgrade docs says about that plugin that "The version is now managed by the Grails BOM, so it should be removed from the dependency declaration" -- yet the generated build.gradle file (when adding the Quartz Feature) shows that dependency with a version:
> implementation "org.apache.grails:grails-quartz:4.0.0"
If there's a reason that version is needed, a comment explaining why would be helpful -- or, if not, removing the version seems wise
The Web Console Feature also includes a version -- though its coordinates suggest it may not be managed by the Grails BOM, so perhaps it is needed in this case (again, if so, an explanatory comment would be helpful):
> runtimeOnly "org.grails.plugins:grails-web-console:7.0.0"
Thanks for clarifying these minor questions!
Re: Grails 7 migration question: Javax vs Jakarta on error page?
Posted by Søren Berg Glasius <sb...@apache.org>.
This should be fixed in Grails 8.0.0-RC2
https://github.com/apache/grails-core/pull/16379
Den ons. 23. sep. 2026 kl. 07.14 skrev Søren Berg Glasius <
sbglasius@apache.org>:
> Hi,
>
> It looks wrong to me, so I've created an issue
> https://github.com/apache/grails-core/issues/16378 and I'm pushing a fix
> for it as well.
>
> Den tirs. 22. sep. 2026 kl. 17.38 skrev J. Jason, DJ - FM/AM <
> JJasonDJFMAM@proton.me>:
>
>> The */views/error.gsp* page generated by the Grails Forge still
>> references *javax.servlet.error.exception* -- should that be
>> *jakarta.servlet.error.exception*, or am I missing something about the
>> javax => jakarta migration?
>>
>> [image: Screenshot 2026-09-22 at 10.13.36 AM.png]
>>
>> FWIW, both packages are mentioned together in
>> https://github.com/jakartaee/servlet/issues/388, suggesting they are
>> equivalent-ish...but I'm very new to this, so I could easily be mistaken.
>>
>>
>> --
>>
>> Best regards
>> Søren Berg Glasius
>>
>> Apache Groovy™ and Apache Grails® PMC
>> --- Press ESC once to quit - twice to save the changes.
>>
>
--
Best regards
Søren Berg Glasius
Apache Groovy™ and Apache Grails® PMC
--- Press ESC once to quit - twice to save the changes.
Re: Grails 7 migration question: Javax vs Jakarta on error page?
Posted by Søren Berg Glasius <sb...@apache.org>.
Hi,
It looks wrong to me, so I've created an issue
https://github.com/apache/grails-core/issues/16378 and I'm pushing a fix
for it as well.
Den tirs. 22. sep. 2026 kl. 17.38 skrev J. Jason, DJ - FM/AM <
JJasonDJFMAM@proton.me>:
> The */views/error.gsp* page generated by the Grails Forge still
> references *javax.servlet.error.exception* -- should that be
> *jakarta.servlet.error.exception*, or am I missing something about the
> javax => jakarta migration?
>
> [image: Screenshot 2026-09-22 at 10.13.36 AM.png]
>
> FWIW, both packages are mentioned together in
> https://github.com/jakartaee/servlet/issues/388, suggesting they are
> equivalent-ish...but I'm very new to this, so I could easily be mistaken.
>
>
> --
>
> Best regards
> Søren Berg Glasius
>
> Apache Groovy™ and Apache Grails® PMC
> --- Press ESC once to quit - twice to save the changes.
>