Maven import: can't use relative path for project files
Answered
This is about the maven import. In our setup we would like to tick the checkbox
[X ] Keep project files in
not only in project settings, but also in 'new project settings' to a relative path. This has the background that we would like to have a uniform setup across the team and sync those settings off via settings repository or at least document them someplace. However there seems to be a problem. The box for the path accepts anything, but as the logs show, the path is resolved absolute. I tried using $PROJECT_ROOT$ but that didn't make a difference.
How can I to tell the maven import to keep project files always in for example ./idea-files ?
Please sign in to leave a comment.
>This has the background that we would like to have a uniform setup across the team and sync those settings off via settings repository or at least document them someplace.
Do you mean you want to store the project configuration in a different repository than the project itself?
Please also note that the Settings Repository synchronizes the IDE global settings, not the project settings.
>The box for the path accepts anything, but as the logs show, the path is resolved absolute.
You can not use path macros in the UI dialogs.
But you can try defining the path variable for this. Then whenever a new IDE instans will try to open the path for which this path variable is defined it will ask user to set the location for this variable for their IDE installation (see mentioned web help for more information about Path Variables).
Though please note that in latest versions it is not possible to use this option for Maven projects, please see: https://youtrack.jetbrains.com/issue/IDEA-229122