-
Notifications
You must be signed in to change notification settings - Fork 29
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
IDEasy can not handle a faulty definition of JAVA_HOME #925
Labels
Comments
First of all I think that it is not IDEasy but maven that cannot handle a faulty definition of JAVA_HOME.
|
julia-cap
added a commit
to julia-cap/IDEasy
that referenced
this issue
Jan 30, 2025
- Added JAVA_HOME to IdeVariables - created implementation of EnvironmentContext to retrieve system environment variables
julia-cap
added a commit
to julia-cap/IDEasy
that referenced
this issue
Jan 31, 2025
- Removed JAVA_HOME from IdeVariables - added PathSyntax to variable collector - created EnvironmentVariableType TOOL - setting environmentVariables by implementing withEnvVar() in EnvironmentVariableCollectorContext
julia-cap
added a commit
to julia-cap/IDEasy
that referenced
this issue
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Expected behavior
As an IDEasy user I expect IDEasy to help me fix issues with my Java configuration.
Actual behavior
If I deliberately use a faulty Java configuration e.g. set my JAVA_HOME to a non existent directory, IDEasy will just report an error like this:
Instead if would be better if IDEasy can repair itself or point the user in the right direction to fix this problem.
Steps to reproduce (bug) / Use Case of feature request (enhancement)
export JAVA_HOME="C:/Test"
ide mvn
Related/Dependent Issues
Comments/Hints:
It would for example be helpful, if IDEasy would print out where the JAVA_HOME variable is pointing to.
Affected version:
The text was updated successfully, but these errors were encountered: