Closed hohwille closed 9 months ago
Suggested test:
mvn clean install
)scripts/target/devonfw-ide-scripts-*.tgz
to a new empty folder (e.g. "C:\projects\test").setup.bat
on windows).devon.software.version
file from your IDE_HOME (e.g. "C:\projects\test.devon.software.version").devon
command with some arguments (e.g. devon java setup
) and verify that now the migrations are run.Thanks for the test suggestion.
I've run the test as suggested. The migration did not start in setup and migration started after deleting the .devon.software.version
file.
I've also added the migration check to the environment-project.bat
for windows users.
I have to mention though that the migration only starts when I'm opening a shell through the context menu.
This looks like I have to start the migration from somewhere else (f.e. devon.bat
), to ensure that it is only run when devon
is being used.
As a devonfw-ide user, I want to be able to update my very old IDE installations without problems so that everything is working.
However, when my very old IDE installations are older than
2023.02.001
the migration scripts are not run as the feature to run them was only added in2023.02.001
. But there is a simple solution to add a "self-healing" feature: If the file$DEVON_IDE_HOME/.devon.software.version
is not present, the migration has been missed out and we can simply run$DEVON_IDE_HOME/scripts/migration
to heal this. This workaround can simply be added somewhere here. However, it has to be taken into account that this should not happen on initial setup (devon ide setup
) that also will trigger the linked code-spot (in that case initially there is nosoftware
folder orworkspaces
and if the ide setup creates the.devon.software.version
early enough before invokingdevon
recursive then all should work fine).