You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, JSweet necessarily uses the JAVA_HOME variable. We need a way to configure the JDK without having to change that variable (it is global and may conflict with other Java software).
My favorite method would be to simply get the path from the SDK used by the project, which would have to be a JDK >= 1.8.
As a fallback, we may have a configuration field to set the JDK path in the JSweet preferences.
The text was updated successfully, but these errors were encountered:
That would be my favorite as well. Have in mind that Eclipse does not need the JDK and can happily use a JRE as well (for obvious reasons). So perhaps the jsweet eclipse plugin should indicate to the user that the Java Runtime bound to the jsweet project is not really a JDK but a JRE.
At this point, JSweet necessarily uses the
JAVA_HOME
variable. We need a way to configure the JDK without having to change that variable (it is global and may conflict with other Java software).My favorite method would be to simply get the path from the SDK used by the project, which would have to be a JDK >= 1.8.
As a fallback, we may have a configuration field to set the JDK path in the JSweet preferences.
The text was updated successfully, but these errors were encountered: