Troubleshooting
Find solutions to common issues you might encounter while running a Java Modernization workflow with IBM Bob.
SDKMan or WinGet not detected
Ensure SDKMan is initialized in your shell profile and that you have restarted the terminal session after installation.
- Open your shell profile (
~/.bashrcor~/.zshrc). - Verify that the SDKMan initialization block is present at the bottom of the file.
- Restart your terminal session.
After installing WinGet, restart VS Code and any open terminals so that the updated PATH is picked up by Bob.
If auto-installation is blocked by corporate policy, pre-install the target JDK manually and set JAVA_HOME to point to it.
Dependency resolution errors
Run a clean build to force dependency re-download.
mvn clean install -Ugradle clean build --refresh-dependenciesGit flow integration problems
Confirm that Git is installed and accessible on the system PATH:
git --versionIf the command is not found, install Git for your operating system and ensure it is available on the PATH before restarting Bob.
UI Modernization: missing backend or frontend output
Ensure that the back/ and front/ directories exist in the project root before starting the UI Modernization workflow. These directories must be created manually before initiating the workflow.
AMA bundle issues (Liberty replatforming)
The AMA Migration Bundle must be generated from AMA version 4.6.0 or later.
Check the following if you encounter issues with the AMA bundle:
- The ZIP must contain
server.xml, migration recipes, and dependency analysis at the top level — no extra wrapping folder. - If deployment to Liberty fails, verify that:
- The
server.xmlfeature set matches the installed Liberty version. - The
liberty-maven-pluginversion aligns with your Liberty runtime.
- The