Skip to content
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

[update]java.compiler error #11

Open
yefeiyu opened this issue Dec 30, 2023 · 0 comments
Open

[update]java.compiler error #11

yefeiyu opened this issue Dec 30, 2023 · 0 comments

Comments

@yefeiyu
Copy link

yefeiyu commented Dec 30, 2023

OpenJDK 64-Bit Server VM warning: The java.compiler system property is obsolete and $

The warning message you're encountering, "OpenJDK 64-Bit Server VM warning: The java.compiler system property is obsolete," typically indicates that a part of your Java configuration or code is using a feature or property that is outdated. This warning generally doesn't affect the execution of a Java program, but it suggests that an aspect of your Java setup or code might be employing deprecated features.

How to Address the Warning

  1. Check Java Version:
    Ensure that you're using a Java version that's compatible with your project. Different Java versions might have varying levels of support for certain properties and features.

  2. Review Project Settings:
    If there are JVM arguments or system properties specified in your project or within your Emacs environment, check if the java.compiler property is being used. If it is, consider removing or updating it.

  3. Update Dependencies:
    Make sure that any third-party libraries or frameworks used in your project are up-to-date, as older versions might rely on deprecated features.

  4. Configure lsp-java:
    Examine the configuration of lsp-java to see if there are any relevant settings that need to be updated or adjusted.

  5. Ignore the Warning:
    If this warning doesn't affect the running of your project and you can't pinpoint its exact cause, you might choose to ignore it. However, it's always better to understand the root cause of a warning.

  6. Consult Documentation and Community:
    Look up relevant Java and OpenJDK documentation, as well as Emacs and lsp-java communities and documentation, for more information or solutions related to this warning.

  7. Environment Variables:
    Check your environment variable settings, especially those related to Java and JVM, to ensure there are no outdated or incorrect configurations.

Considerations

  • Warnings typically don't prevent a program from running, but they do provide information about potential issues or areas for improvement.
  • Keep your development environment (like Emacs, lsp-java, Java SDK) up to date to avoid issues caused by outdated tools or configurations.

If you're unable to determine the specific cause of the warning, or if it starts to impact your development work, it's advisable to seek help in relevant development communities or forums, providing more detailed information and context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant