Since the path of these metadata files has been hard-coded in the code as constants during implementation, these constants have been referenced by various Eclipse modules and even plug-ins. The creation of this post can even be traced back to 2004. The official project name of the Java language service used behind the VS Code Java project is Eclipse JDT Language Server™ , which was jointly developed by Microsoft and Red Hat. As you can see in the project architecture diagram above, we reused some Eclipse modules in our implementation , and these automatically generated metadata files are also generated by some of the upstream modules. A related discussion thread can be found in the Eclipse discussion area. JDT Java Language Server architecture diagram The root cause starts with the architecture of Java Language Services: In fact, this is not because our product team does not want to completely fix this problem. As the user base increases, this problem will also likely to cause negative impact for more users. However, due to the problem that the Java extension generates metadata files in the project directory when importing the project, we have received a lot of frustration from the users. With more features introduced into Java extension on Visual Studio Code, the number of our users is also steadily increasing. This blog post shares our journey of solving this problem and the final solution. This issue was reported more than three years ago and it has been there since 2018. classpath, settings, etc.) will no longer be generated in the project path by default. Recent 1.1.0 release of Language Support for Java™ contains an important update: now when the extension imports a new Java project, the project metadata files (. Say Goodbye to Project Files in Visual Studio Code December 21, 2021
0 kommentar(er)
