> On Jan 13, 2026, at 11:32 AM, Christopher Schultz
> <[email protected]> wrote:
>
> Rob,
>>
>
> Maybe I don't understand.
No I do not have both servlet packages after the conversion. But I do still
have other javax imports and am wondering if it is wisest now to move
everything to jakarta now. As I said I applied no command line options to the
tool.
>
> The migration tool should take a project from being Java EE-based to be
> Jakarta EE-based. You shouldn't have code with e.g. imports for both
> javax.servlet and jakarta.servlet. That would never compile.
Yeah, totally get the boundaries of the tool.
>
> What am I missing about your situation/question?
>
I am sure the confusion is my fault. I assume I can use the latest jakarta
release (11)?
Thanks again for all your time,
rjs
>>> Then switch any dependencies you know about for their Jakarta equivalents.
>>> Then build and test, swapping-out anything that isn't working for its
>>> Jakarta equivalent.
>>>
>>> For those packages which aren't available targeted at the Jakarta APIs, run
>>> those JAR files through the converter either as a part of your build or
>>> pre-build with stored-local JAR files.
>>>
>>> -chris
>>>
>> Not sure if there's any attempt to address any of the build environments,
>> but if so adding gradle's build.gradle files to the mix would be greatly
>> appreciated.
>
> I'm totally ignorant of Gradle, other than that it's a build too. The
> migration tool doesn't have any opinions about any toolchains. You can feel
> free to integrate into your build process in whatever way you prefer.
>
> -chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
