You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "matinh (via GitHub)" <gi...@apache.org> on 2023/05/31 06:46:08 UTC

[GitHub] [maven-mvnd] matinh commented on issue #619: Problem when running in Cygwin with an existed env variable “JAVA_HOME”.

matinh commented on issue #619:
URL: https://github.com/apache/maven-mvnd/issues/619#issuecomment-1569587503

   Just for the records and maybe to help someone else. I had a very similar problem but without the cygwin environment. `mvnd` always reported some not existing path (old java version) with the same exception as above. After some searching in environment variables and config files, I found the reason: I had an old `~/.m2/mvnd.properties` with java.home set to the obsolete path. Removing this file solved the problem.
   
   Maybe it would be nice if `mvnd` would report where it got the java path from, at least in case of an error.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org