-
Notifications
You must be signed in to change notification settings - Fork 301
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
Cannot save config file 'FileBasedConfig[H:\.config\jgit\config]' #566
Comments
Hello, For the time being you could potentially switch to the native git binary via |
Ah I just realized that this is essentially a duplicate of #518. At least it's the same issue. Perhaps a different context....not sure if I should keep both issues open, but I guess it doesn't hurt either. |
The difference with #518 is that there the build fails while in this case it does not thanks for the useNativeGit tip! |
thanks for pointing out that difference! |
Same problem here with 4.9.10:
doesn't make a difference |
Sorry it should have been |
@TheSnoozer we're actually observing the same problem now in VirtusLab/git-machete-intellij-plugin#1239 ... despite using the latest JGit ( |
Thanks for raising this! I guess we should then (re-)open a ticket with jgit :-( |
Yes, if you could 🙏🏻 pls mention me on that ticket (if that's on GitHub) or provide the link for the ticket (otherwise) 🎫 |
Actually... seems that it can be closed: VirtusLab/git-machete-intellij-plugin#1239 (comment) |
Hi everyone. I came across the same issue on the gradle plugin for git commit id. To rule solutions out, I tried to create the .config directory manually and that works correctly. I also tried to manually exclude the jgit dependency and manually include newer versions which still produced the error. Did anyone find the cause of this that could maybe be applied to the gradle plugin also? Thanks |
Describe the bug
During maven build, we observe the following error message from git-commit-id-maven-plugin 4.0.5:
The H: drive is a network drive where our home dir is set
Steps to Reproduce
mvn -version
This error doesn not prevents the maven build from being executed with success. However, intelliJ Community 2019.3 spots it as an error:
Expected behavior
Additional context
This might be similar to https://www.eclipse.org/forums/index.php/t/1103395/
The text was updated successfully, but these errors were encountered: