IMHO we cannot easily repair what has already happened out there in the wild.
We could change ${DEVON_IDE_HOME}/software/maven to ${MAVEN_HOME} instead of ${DEVON_IDE_HOME}/software/mvn but all forks of our settings would need to upstream merge this change or they are broken.
Should we add a temporary workaround to create a symlink maven pointing to mvn in a migration script or is there any other/better solution? Or is it even better that all projects need to get aware of the problem and "repair" their settings?
Expected behavior
As a devonfw-ide user, I want a consistent project setup so that all works (including maven in Eclipse or Intellij)
Actual behavior
After default setup, my Eclipse configuration is broken as the maven installation points to a non-existing directory.
Steps to reproduce (bug) / Use Case of feature request (enhancement)
devon eclipse
Related/Dependent Issues
1085
Comments/Hints:
https://github.com/devonfw/ide-settings/blob/7710bfef774c548199bcfca3b6f010427c77bed6/eclipse/workspace/update/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.m2e.core.prefs#L10
IMHO we cannot easily repair what has already happened out there in the wild. We could change
${DEVON_IDE_HOME}/software/maven
to${MAVEN_HOME}
instead of${DEVON_IDE_HOME}/software/mvn
but all forks of our settings would need to upstream merge this change or they are broken.Should we add a temporary workaround to create a symlink
maven
pointing tomvn
in a migration script or is there any other/better solution? Or is it even better that all projects need to get aware of the problem and "repair" their settings?Affected version: