Skip to content

#1209: improve confusing migration version message - #2611

Open
Ali-Shariati-Najafabadi wants to merge 1 commit into
devonfw:mainfrom
Ali-Shariati-Najafabadi:feature/1209-improve-migration-status-message
Open

Ali-Shariati-Najafabadi wants to merge 1 commit into
devonfw:mainfrom
Ali-Shariati-Najafabadi:feature/1209-improve-migration-status-message

Conversation

@Ali-Shariati-Najafabadi

@Ali-Shariati-Najafabadi Ali-Shariati-Najafabadi commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

This PR fixes #1209

Implemented changes:

  • Reworded the migration message of ide status in StatusCommandlet.logMigrationStatus() so it is understandable for end-users: Your project '«project-name»' was created or last updated with IDEasy version «version» and needs an update.
  • Removed the internal migration target version from the message, as it was confused with the installed IDEasy version.
  • Added tests to StatusCommandletTest for an outdated project and for an up-to-date project.
  • Added the issue to CHANGELOG.adoc.

Testing instructions

  1. Go to an existing IDEasy project and set an old version in the file .ide.software.version in the project root (e.g. 2025.01.001-beta).
  2. Run ide status.
  3. Verify that the message Your project '«project-name»' was created or last updated with IDEasy version 2025.01.001-beta and needs an update. followed by Please run 'ide update' to migrate your project. is shown and that no migration target version is mentioned.
  4. Run ide update and then ide status again and verify that the message is no longer shown.
  5. Alternatively run mvn -Dtest=StatusCommandletTest test in the cli folder.

Checklist for this PR

  • When running mvn clean test locally all tests pass and build is successful
  • PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat and not feature/921 fixed setup.bat). If no issue ID exists, title only.
  • PR top-level comment summaries what has been done and contains link to addressed issue(s)
  • PR and issue(s) have suitable labels
  • Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
  • You followed all coding conventions
  • You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labelled
    with internal
  • You have not changed any dependency in pom.xml files or otherwise if runtime dependencies changed, you have updated our LICENSE.asciidoc
  • You have formulated clear instructions on how to test your contribution under "Testing instructions"

@Ali-Shariati-Najafabadi
Ali-Shariati-Najafabadi force-pushed the feature/1209-improve-migration-status-message branch from d3b4bed to 0eb716a Compare October 4, 2026 18:33
@coveralls

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 37224898538

Coverage increased (+0.02%) to 74.146%

Details

  • Coverage increased (+0.02%) from the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • 3 coverage regressions across 2 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

3 previously-covered lines in 2 files lost coverage.

File Lines Losing Coverage Coverage
com/devonfw/tools/ide/commandlet/StatusCommandlet.java 2 81.37%
com/devonfw/tools/ide/version/VersionSegment.java 1 91.6%

Coverage Stats

Coverage Status
Relevant Lines: 19564
Covered Lines: 15164
Line Coverage: 77.51%
Relevant Branches: 8679
Covered Branches: 5777
Branch Coverage: 66.56%
Branches in Coverage %: Yes
Coverage Strength: 3.32 hits per line

💛 - Coveralls

@JoelAdbu JoelAdbu left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Ali-Shariati-Najafabadi well Done! I tested it locally everything works just as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 👀 In review

Development

Successfully merging this pull request may close these issues.

migration version message is confusing

3 participants