-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Folder ${M2_REPO} gets created #706
Comments
I have been able to reproduce the problem. With settings, you can add an option to the command to read the settings. Then it seems to work. Now I am getting an error: @hohwille What do you think about it? |
I have seen similar issues just working on cobigen. |
My suggestion for the next steps is:
Suggestion for these stepwise changes:
If no
Now in eclipse ensure the newly created project ( |
The problem is caused because the ${M2_REPO} variable is not resolved in conf/.m2/repository/settings.xml (...). This creates a folder with the same name as the variable when adding Maven dependencies in Eclipse. I could fix the bug by updating the following M2E Plugin in Eclipse. M2E - POM Editor using LemMinX language Server |
Thank you for your analysis. So my assumption and gut feeling was kind of correct. |
Thank you @alfeilex for the analysis and the fix 👍 |
Expected behavior
All maven artifacts should go to the local maven repo configured via
devon.properties
(by default$DEVON_IDE_HOME/conf/.m2/repository
but can also be changed to e.g.~/.m2/repository
viadevon.properties
).Actual behavior
For some odd reason some tool or script causes a folder named
${M2_REPO}
being created in the top-level IDE installation$DEVON_IDE_HOME
).Steps to reproduce (bug) / Use Case of feature request (enhancement)
${M2_REPO}
folder appears and is filled with some maven artifacts.Related/Dependent Issues
Comments/Hints:
Seems as if at some point
${M2_REPO}
is used as variable but does not properly get resolved leading to the fact that it is used as relative path for the maven repository created as folder.Affected version:
The text was updated successfully, but these errors were encountered: