Giter VIP home page Giter VIP logo

vscode-java's Introduction

Language support for Java ™ for Visual Studio Code

Visual Studio Marketplace Installs Join the chat at https://gitter.im/redhat-developer/vscode-java Build Status License

Provides Java ™ language support via Eclipse ™ JDT Language Server, which utilizes Eclipse ™ JDT, M2Eclipse and Buildship.

Quick Start

  1. Install the Extension
  2. On the following platforms, the extension should activate without any setup : win32-x64, darwin-x64, darwin-arm64, linux-x64, linux-arm64.
    If on another platform, or using the "universal" version, you can set a Java Development Kit. It must be Java 17 or above.
  3. Optionally, download and install a Java Development Kit for your project (Java 1.5 or above is supported). See Project JDKs for more details
  4. Extension is activated when you first access a Java file
    • Recognizes projects with Maven or Gradle build files in the directory hierarchy.

Features

screencast

  • Supports code from Java 1.5 to Java 22
  • Maven pom.xml project support
  • Gradle project support (with experimental Android project import support)
  • Standalone Java files support
  • As-you-type reporting of parsing and compilation errors
  • Code completion
  • Code/Source actions / Refactoring
  • Javadoc hovers
  • Organize imports
    • triggered manually or on save
    • when pasting code into a java file with Ctrl+Shift+v (Cmd+Shift+v on Mac).
  • Type search
  • Code outline
  • Code folding
  • Code navigation
  • Code lens (references/implementations)
  • Highlights
  • Code formatting (on-type/selection/file)
  • Code snippets
  • Annotation processing support (automatic for Maven projects)
  • Semantic selection
  • Diagnostic tags
  • Call Hierarchy
  • Type Hierarchy

To launch and debug your Java programs, it's recommended you install Java Debug Extension for Visual Studio Code.

See the changelog for the latest release. You might also find useful information in the project Wiki.

Setting the JDK

Java Tooling JDK

Now that Java extension will publish platform specific versions, it will embed a JRE for supported platforms such as win32-x64, linux-x64, linux-arm64, darwin-x64, darwin-arm64. The embedded JRE is used to launch the Language Server for Java. Users are only responsible for configuring Project JDKs to compile your Java projects.

The following part is only kept for the universal version without embedded JRE.

The tooling JDK will be used to launch the Language Server for Java. And by default, will also be used to compile your projects. Java 17 is the minimum required version.

The path to the Java Development Kit can be specified by the java.jdt.ls.java.home setting in VS Code settings (workspace/user settings). If not specified, it is searched in the following order until a JDK meets current minimum requirement.

  • the JDK_HOME environment variable
  • the JAVA_HOME environment variable
  • on the current system path

Project JDKs

If you need to compile your projects against a different JDK version, it's recommended you configure the java.configuration.runtimes property in your user settings, eg:

"java.configuration.runtimes": [
  {
    "name": "JavaSE-1.8",
    "path": "/path/to/jdk-8",
  },
  {
    "name": "JavaSE-11",
    "path": "/path/to/jdk-11",
  },
  {
    "name": "JavaSE-22",
    "path": "/path/to/jdk-22",
    "default": true
  },
]

The default runtime will be used when you open standalone Java files.

Available commands

The following commands are available:

  • Switch to Standard Mode: switches the Java Language Server to Standard mode. This command is only available when the Java Language Server is in LightWeight mode.
  • Java: Reload Projects (Shift+Alt+U): It forces project configuration / classpath updates (eg. dependency changes or Java compilation level), according to the project build descriptor.
  • Java: Import Java Projects into Workspace: detects and imports all the Java projects into the Java Language Server workspace.
  • Java: Open Java Language Server Log File: opens the Java Language Server log file, useful for troubleshooting problems.
  • Java: Open Java Extension Log File: opens the Java extension log file, useful for troubleshooting problems.
  • Java: Open All Log Files: opens both the Java Language Server log file and the Java extension log file.
  • Java: Force Java Compilation (Shift+Alt+B): manually triggers compilation of the workspace.
  • Java: Rebuild Projects: manually triggers a full build of the selected projects.
  • Java: Open Java Formatter Settings: opens the Eclipse formatter settings. Creates a new settings file if none exists.
  • Java: Clean Java Language Server Workspace: cleans the Java language server workspace.
  • Java: Attach Source: attaches a jar/zip source to the currently opened binary class file. This command is only available in the editor context menu.
  • Java: Add Folder to Java Source Path: adds the selected folder to its project source path. This command is only available in the file explorer context menu and only works for unmanaged folders.
  • Java: Remove Folder from Java Source Path: removes the selected folder from its project source path. This command is only available in the file explorer context menu and only works for unmanaged folders.
  • Java: List All Java Source Paths: lists all the Java source paths recognized by the Java Language Server workspace.
  • Java: Show Build Job Status: shows the Java Language Server job status in Visual Studio Code terminal.
  • Java: Go to Super Implementation: goes to the super implementation for the current selected symbol in editor.
  • Java: Restart Java Language Server: restarts the Java language server.

Supported VS Code settings

The following settings are supported:

  • java.home : Deprecated, please use 'java.jdt.ls.java.home' instead. Absolute path to JDK home folder used to launch the Java Language Server. Requires VS Code restart.

  • java.jdt.ls.lombokSupport.enabled: Whether to enable lombok support. Defaults to true.

  • java.jdt.ls.vmargs : Extra VM arguments used to launch the Java Language Server. Requires VS Code restart.

  • java.errors.incompleteClasspath.severity : Specifies the severity of the message when the classpath is incomplete for a Java file. Supported values are ignore, info, warning, error.

  • java.trace.server : Traces the communication between VS Code and the Java language server.

  • java.configuration.updateBuildConfiguration : Specifies how modifications on build files update the Java classpath/configuration. Supported values are disabled (nothing happens), interactive (asks about updating on every modification), automatic (updating is automatically triggered).

  • java.configuration.maven.userSettings : Path to Maven's user settings.xml.

  • java.configuration.checkProjectSettingsExclusions: Deprecated, please use 'java.import.generatesMetadataFilesAtProjectRoot' to control whether to generate the project metadata files at the project root. And use 'files.exclude' to control whether to hide the project metadata files from the file explorer. Controls whether to exclude extension-generated project settings files (.project, .classpath, .factorypath, .settings/) from the file explorer. Defaults to false.

  • java.referencesCodeLens.enabled : Enable/disable the references code lenses.

  • java.implementationsCodeLens.enabled : Enable/disable the implementations code lenses.

  • java.signatureHelp.enabled : Enable/disable signature help support (triggered on ().

  • java.signatureHelp.description.enabled : Enable/disable to show the description in signature help. Defaults to false.

  • java.contentProvider.preferred : Preferred content provider (see 3rd party decompilers available in vscode-java-decompiler).

  • java.import.exclusions : Exclude folders from import via glob patterns. Use ! to negate patterns to allow subfolders imports. You have to include a parent directory. The order is important.

  • java.import.gradle.enabled : Enable/disable the Gradle importer.

  • Specify the Gradle distribution used by the Java extension:

    • java.import.gradle.wrapper.enabled: Use Gradle from the 'gradle-wrapper.properties' file. Defaults to true.
    • java.import.gradle.version: Use Gradle from the specific version if the Gradle wrapper is missing or disabled.
    • java.import.gradle.home: Use Gradle from the specified local installation directory or GRADLE_HOME if the Gradle wrapper is missing or disabled and no 'java.import.gradle.version' is specified.

  • java.import.gradle.arguments: Arguments to pass to Gradle.

  • java.import.gradle.jvmArguments: JVM arguments to pass to Gradle.

  • java.import.gradle.user.home: setting for GRADLE_USER_HOME.

  • java.import.gradle.offline.enabled: Enable/disable the Gradle offline mode. Defaults to false.

  • java.import.maven.enabled : Enable/disable the Maven importer.

  • java.autobuild.enabled : Enable/disable the 'auto build'.

  • java.maxConcurrentBuilds: Set max simultaneous project builds.

  • java.completion.enabled : Enable/disable code completion support.

  • java.completion.guessMethodArguments : Specify how the arguments will be filled during completion. Defaults to auto.

    • auto: Use off only when using Visual Studio Code - Insiders, other platform will defaults to insertBestGuessedArguments.
    • off: Method arguments will not be inserted during completion.
    • insertParameterNames: The parameter names will be inserted during completion.
    • insertBestGuessedArguments: The best guessed arguments will be inserted during completion according to the code context.

  • java.completion.filteredTypes: Defines the type filters. All types whose fully qualified name matches the selected filter strings will be ignored in content assist or quick fix proposals and when organizing imports. For example 'java.awt.*' will hide all types from the awt packages.

  • java.completion.favoriteStaticMembers : Defines a list of static members or types with static members.

  • java.completion.importOrder : Defines the sorting order of import statements.

  • java.format.enabled : Enable/disable the default Java formatter.

  • java.format.settings.url : Specifies the url or file path to the Eclipse formatter xml settings.

  • java.format.settings.profile : Optional formatter profile name from the Eclipse formatter settings.

  • java.format.comments.enabled : Includes the comments during code formatting.

  • java.format.onType.enabled : Enable/disable on-type formatting (triggered on ;, } or <return>).

  • java.foldingRange.enabled: Enable/disable smart folding range support. If disabled, it will use the default indentation-based folding range provided by VS Code.

  • java.maven.downloadSources: Enable/disable download of Maven source artifacts as part of importing Maven projects.

  • java.maven.updateSnapshots: Force update of Snapshots/Releases. Defaults to false.

  • java.codeGeneration.hashCodeEquals.useInstanceof: Use 'instanceof' to compare types when generating the hashCode and equals methods. Defaults to false.

  • java.codeGeneration.hashCodeEquals.useJava7Objects: Use Objects.hash and Objects.equals when generating the hashCode and equals methods. This setting only applies to Java 7 and higher. Defaults to false.

  • java.codeGeneration.useBlocks: Use blocks in 'if' statements when generating the methods. Defaults to false.

  • java.codeGeneration.generateComments: Generate method comments when generating the methods. Defaults to false.

  • java.codeGeneration.toString.template: The template for generating the toString method. Defaults to ${object.className} [${member.name()}=${member.value}, ${otherMembers}].

  • java.codeGeneration.toString.codeStyle: The code style for generating the toString method. Defaults to STRING_CONCATENATION.

  • java.codeGeneration.toString.skipNullValues: Skip null values when generating the toString method. Defaults to false.

  • java.codeGeneration.toString.listArrayContents: List contents of arrays instead of using native toString(). Defaults to true.

  • java.codeGeneration.toString.limitElements: Limit number of items in arrays/collections/maps to list, if 0 then list all. Defaults to 0.

  • java.selectionRange.enabled: Enable/disable Smart Selection support for Java. Disabling this option will not affect the VS Code built-in word-based and bracket-based smart selection.

  • java.showBuildStatusOnStart.enabled: Automatically show build status on startup, defaults to notification.

    • notification: Show the build status via progress notification.
    • terminal: Show the build status via terminal.
    • off: Do not show any build status.

    For backward compatibility, this setting also accepts boolean value, where true has the same meaning as notification and false has the same meaning as off.

  • java.project.outputPath: A relative path to the workspace where stores the compiled output. Only effective in the WORKSPACE scope. The setting will NOT affect Maven or Gradle project.

  • java.project.referencedLibraries: Configure glob patterns for referencing local libraries to a Java project.

  • java.completion.maxResults: Maximum number of completion results (not including snippets). 0 (the default value) disables the limit, all results are returned. In case of performance problems, consider setting a sensible limit.

  • java.configuration.runtimes: Map Java Execution Environments to local JDKs.

  • java.server.launchMode:

    • Standard: Provides full features such as intellisense, refactoring, building, Maven/Gradle support etc.
    • LightWeight: Starts a syntax server with lower start-up cost. Only provides syntax features such as outline, navigation, javadoc, syntax errors. The lightweight mode won't load thirdparty extensions, such as java test runner, java debugger, etc.
    • Hybrid: Provides full features with better responsiveness. It starts a standard language server and a secondary syntax server. The syntax server provides syntax features until the standard server is ready. And the syntax server will be shutdown automatically after the standard server is fully ready.

    Default launch mode is Hybrid. Legacy mode is Standard

  • java.sources.organizeImports.starThreshold: Specifies the number of imports added before a star-import declaration is used, default is 99.

  • java.sources.organizeImports.staticStarThreshold: Specifies the number of static imports added before a star-import declaration is used, default is 99.

  • java.imports.gradle.wrapper.checksums: Defines allowed/disallowed SHA-256 checksums of Gradle Wrappers.

  • java.project.importOnFirstTimeStartup: Specifies whether to import the Java projects, when opening the folder in Hybrid mode for the first time. Supported values are disabled (never imports), interactive (asks to import or not), automatic (always imports). Default to automatic.

  • java.project.importHint: Enable/disable the server-mode switch information, when Java projects import is skipped on startup. Defaults to true.

  • java.import.gradle.java.home: Specifies the location to the JVM used to run the Gradle daemon.

  • java.project.resourceFilters: Excludes files and folders from being refreshed by the Java Language Server, which can improve the overall performance. For example, ["node_modules",".git"] will exclude all files and folders named 'node_modules' or '.git'. Pattern expressions must be compatible with java.util.regex.Pattern. Defaults to ["node_modules",".git"].

  • java.templates.fileHeader: Specifies the file header comment for new Java file. Supports configuring multi-line comments with an array of strings, and using ${variable} to reference the predefined variables.

  • java.templates.typeComment: Specifies the type comment for new Java type. Supports configuring multi-line comments with an array of strings, and using ${variable} to reference the predefined variables.

  • java.references.includeAccessors: Include getter, setter and builder/constructor when finding references. Default to true.

  • java.configuration.maven.globalSettings : Path to Maven's global settings.xml.

  • java.configuration.maven.lifecycleMappings : Path to Maven's lifecycle mappings xml.

  • java.eclipse.downloadSources : Enable/disable download of Maven source artifacts for Eclipse projects.

  • java.references.includeDecompiledSources : Include the decompiled sources when finding references. Default to true.

  • java.project.sourcePaths: Relative paths to the workspace where stores the source files. Only effective in the WORKSPACE scope. The setting will NOT affect Maven or Gradle project.

  • java.typeHierarchy.lazyLoad: Enable/disable lazy loading the content in type hierarchy. Lazy loading could save a lot of loading time but every type should be expanded manually to load its content.

  • java.codeGeneration.insertionLocation: Specifies the insertion location of the code generated by source actions. Defaults to afterCursor.

    • afterCursor: Insert the generated code after the member where the cursor is located.
    • beforeCursor: Insert the generated code before the member where the cursor is located.
    • lastMember: Insert the generated code as the last member of the target type.

  • java.codeGeneration.addFinalForNewDeclaration: Whether to generate the 'final' modifer for code actions that create new declarations. Defaults to none.

    • none: Do not generate final modifier
    • fields: Generate 'final' modifier only for new field declarations
    • variables: Generate 'final' modifier only for new variable declarations
    • all: Generate 'final' modifier for all new declarations

  • java.settings.url : Specifies the url or file path to the workspace Java settings. See Setting Global Preferences

  • java.symbols.includeSourceMethodDeclarations : Include method declarations from source files in symbol search. Defaults to false.

  • java.quickfix.showAt : Show quickfixes at the problem or line level.

  • java.configuration.workspaceCacheLimit : The number of days (if enabled) to keep unused workspace cache data. Beyond this limit, cached workspace data may be removed.

  • java.import.generatesMetadataFilesAtProjectRoot : Specify whether the project metadata files(.project, .classpath, .factorypath, .settings/) will be generated at the project root. Defaults to false.

  • java.inlayHints.parameterNames.enabled: Enable/disable inlay hints for parameter names. Supported values are: none(disable parameter name hints), literals(Enable parameter name hints only for literal arguments) and all(Enable parameter name hints for literal and non-literal arguments). Defaults to literals.

  • java.compile.nullAnalysis.nonnull: Specify the Nonnull annotation types to be used for null analysis. If more than one annotation is specified, then the topmost annotation will be used first if it exists in your project dependencies. This setting will be ignored if java.compile.nullAnalysis.mode is set to disabled.

  • java.compile.nullAnalysis.nullable: Specify the Nullable annotation types to be used for null analysis. If more than one annotation is specified, then the topmost annotation will be used first if it exists in your project dependencies. This setting will be ignored if java.compile.nullAnalysis.mode is set to disabled.

  • java.compile.nullAnalysis.nonnullbydefault: Specify the NonNullByDefault annotation types to be used for null analysis. If more than one annotation is specified, then the topmost annotation will be used first if it exists in your project dependencies. This setting will be ignored if java.compile.nullAnalysis.mode is set to disabled.

  • java.import.maven.offline.enabled: Enable/disable the Maven offline mode. Defaults to false.

  • java.codeAction.sortMembers.avoidVolatileChanges: Reordering of fields, enum constants, and initializers can result in semantic and runtime changes due to different initialization and persistence order. This setting prevents this from occurring. Defaults to true.

  • java.jdt.ls.protobufSupport.enabled: Specify whether to automatically add Protobuf output source directories to the classpath. Note: Only works for Gradle com.google.protobuf plugin 0.8.4 or higher. Defaults to true.

  • java.jdt.ls.androidSupport.enabled: [Experimental] Specify whether to enable Android project importing. When set to auto, the Android support will be enabled in Visual Studio Code - Insiders. Note: Only works for Android Gradle Plugin 3.2.0 or higher. Defaults to auto.

  • java.completion.postfix.enabled: Enable/disable postfix completion support. Defaults to true.

  • java.completion.chain.enabled: Enable/disable chain completion support. Defaults to false.

  • java.completion.matchCase: Specify whether to match case for code completion. Defaults to firstLetter.

  • java.compile.nullAnalysis.mode: Specify how to enable the annotation-based null analysis. Supported values are disabled (disable the null analysis), interactive (asks when null annotation types are detected), automatic (automatically enable null analysis when null annotation types are detected). Defaults to interactive.

  • java.cleanup.actionsOnSave: Deprecated, please use 'java.cleanup.actions' instead. The list of clean ups to be run on the current document when it's saved. Clean ups can automatically fix code style or programming mistakes. Click here to learn more about what each clean up does.

  • java.cleanup.actions: The list of clean ups to be run on the current document when it's saved or when the cleanup command is issued. Clean ups can automatically fix code style or programming mistakes. Click here to learn more about what each clean up does.

  • java.saveActions.cleanup: Enable/disable cleanup actions on save.

  • java.import.gradle.annotationProcessing.enabled: Enable/disable the annotation processing on Gradle projects and delegate to JDT APT. Only works for Gradle 5.2 or higher.

  • java.sharedIndexes.enabled: [Experimental] Specify whether to share indexes between different workspaces. Defaults to auto and the shared indexes is automatically enabled in Visual Studio Code - Insiders.

    • auto
    • on
    • off

  • java.sharedIndexes.location: Specifies a common index location for all workspaces. See default values as follows:

    • Windows: First use "$APPDATA\\.jdt\\index", or "~\\.jdt\\index" if it does not exist
    • macOS: "~/Library/Caches/.jdt/index"
    • Linux: First use "$XDG_CACHE_HOME/.jdt/index", or "~/.cache/.jdt/index" if it does not exist

  • java.refactoring.extract.interface.replace: Specify whether to replace all the occurrences of the subtype with the new extracted interface. Defaults to true.

  • java.import.maven.disableTestClasspathFlag : Enable/disable test classpath segregation. When enabled, this permits the usage of test resources within a Maven project as dependencies within the compile scope of other projects. Defaults to false.

  • java.configuration.maven.defaultMojoExecutionAction : Specifies default mojo execution action when no associated metadata can be detected. Defaults to ignore.

  • java.completion.lazyResolveTextEdit.enabled: [Experimental] Enable/disable lazily resolving text edits for code completion. Defaults to true.

  • java.edit.validateAllOpenBuffersOnChanges: Specifies whether to recheck all open Java files for diagnostics when editing a Java file. Defaults to false.

  • java.editor.reloadChangedSources: Specifies whether to reload the sources of the open class files when their source jar files are changed. Defaults to ask.

    • ask: Ask to reload the sources of the open class files
    • auto: Automatically reload the sources of the open class files
    • manual: Manually reload the sources of the open class files

  • java.edit.smartSemicolonDetection.enabled: Defines the smart semicolon detection. Defaults to false.

  • java.configuration.detectJdksAtStart: Automatically detect JDKs installed on local machine at startup. If you have specified the same JDK version in java.configuration.runtimes, the extension will use that version first. Defaults to true.

  • java.completion.collapseCompletionItems: Enable/disable the collapse of overloaded methods in completion items. Overrides java.completion.guessMethodArguments. Defaults to false.

Semantic Highlighting

Semantic Highlighting fixes numerous syntax highlighting issues with the default Java Textmate grammar. However, you might experience a few minor issues, particularly a delay when it kicks in, as it needs to be computed by the Java Language server, when opening a new file or when typing. Semantic highlighting can be disabled for all languages using the editor.semanticHighlighting.enabled setting, or for Java only using language-specific editor settings.

Troubleshooting

  1. Check the status of the language tools on the lower right corner (marked with A on image below). It should show ready (thumbs up) as on the image below. You can click on the status and open the language tool logs for further information in case of a failure.

status indicator

  1. Read the troubleshooting guide for collecting informations about issues you might encounter.

  2. Report any problems you face to the project.

Contributing

This is an open source project open to anyone. Contributions are extremely welcome!

For information on getting started, refer to the CONTRIBUTING instructions.

Continuous Integration builds can be installed from http://download.jboss.org/jbosstools/jdt.ls/staging/. Download the most recent java-<version>.vsix file and install it by following the instructions here. Stable releases are archived under http://download.jboss.org/jbosstools/static/jdt.ls/stable/.

Also, you can contribute your own VS Code extension to enhance the existing features by following the instructions here.

Feedback

License

EPL 2.0, See LICENSE for more information.

vscode-java's People

Contributors

0dind avatar aeschli avatar akaroml avatar ansyral avatar apupier avatar codemee avatar cscherryy avatar datho7561 avatar dependabot[bot] avatar eskibear avatar fbricon avatar fvclaus avatar gayanper avatar gorkem avatar hopehadfield avatar jdneo avatar jessicajhee avatar leonovecsergey avatar mathieufortin01 avatar mavaddat avatar mkeller avatar nikolaskomonen avatar rgrunber avatar robstryker avatar snjeza avatar testforstephen avatar timolehto avatar vigilans avatar xiaoyuhao avatar yaohaizh avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

aeschli pmuir pcmind celador fbricon razumit waffle-iron summerstream jpospychala gorkem minipotato uk702 abhishekgahlot francescou dgolovin neumimto snjeza jaydevops duongdainghia psdgithub vscjavaci yaohaizh sharebiguo kartikmsk akshayapr mskarthi95 suriyans egamma reddyshalini lingfenger iyangxicong kbh88zz yangzx554 hspeed bawachhe mowzey123 easyaspi314 fdof anrainie arainie fjsnogueiracx ricardope3 gitter-badger fuminchao btstream boy12371 invinciblejai 38leinad paulvi ws-os ws-development ws-apps ws-tools ws-java mukteshkrmishra nierajsingh kdvolder mjbvz kellis5137 andreysaksonov lostintangent mfeltman sonanipankaj buibup echads rikucherry1993 privat1 jdneo nickboldt mainxx saurabh-sp-tripathi thadhouse xzammy raggamufia shuxiangguo cybernetics prateek-parashar lukaszkolodziejczyk chan099 booshroot arambekverdyan noseglid testforstephen apupier marlon407 xjc90s langkunye secondsun stan-powerpro farismundhir ceazy79 superadmini ghmoore morristech badsyntax tonytamwk benoitf rectcircle autozimu useragent007

vscode-java's Issues

Problem getting code lense for app

Hi --,

I've used the following maven command to create a project
mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=create-device-identity -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false

When I open the project I get the following error message:

[Error - 15:44:09] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:09] 12.10.2016 15:44:02 Problem with codeComplete forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.Openable.getBuffer(Openable.java:285)
    at org.jboss.tools.vscode.java.internal.handlers.CompletionHandler.computeContentAssist(CompletionHandler.java:72)
    at org.jboss.tools.vscode.java.internal.handlers.CompletionHandler.handle(CompletionHandler.java:43)
    at org.jboss.tools.vscode.java.internal.handlers.CompletionHandler.handle(CompletionHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:16] 12.10.2016 15:44:02 Problem with compute occurrences forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.Openable.getBuffer(Openable.java:285)
    at org.jboss.tools.vscode.java.internal.handlers.DocumentHighlightHandler.computeOccurrences(DocumentHighlightHandler.java:50)
    at org.jboss.tools.vscode.java.internal.handlers.DocumentHighlightHandler.handle(DocumentHighlightHandler.java:97)
    at org.jboss.tools.vscode.java.internal.handlers.DocumentHighlightHandler.handle(DocumentHighlightHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:17] 12.10.2016 15:44:02 Problem with compute occurrences forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.Openable.getBuffer(Openable.java:285)
    at org.jboss.tools.vscode.java.internal.handlers.DocumentHighlightHandler.computeOccurrences(DocumentHighlightHandler.java:50)
    at org.jboss.tools.vscode.java.internal.handlers.DocumentHighlightHandler.handle(DocumentHighlightHandler.java:97)
    at org.jboss.tools.vscode.java.internal.handlers.DocumentHighlightHandler.handle(DocumentHighlightHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:44] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:45] 12.10.2016 15:44:02 Problem with codeComplete forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.Openable.getBuffer(Openable.java:285)
    at org.jboss.tools.vscode.java.internal.handlers.CompletionHandler.computeContentAssist(CompletionHandler.java:72)
    at org.jboss.tools.vscode.java.internal.handlers.CompletionHandler.handle(CompletionHandler.java:43)
    at org.jboss.tools.vscode.java.internal.handlers.CompletionHandler.handle(CompletionHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:45] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:46] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:49] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:50] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:50] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[Error - 15:44:51] 12.10.2016 15:44:02 Problem getting code lenses forApp.java
create-device-identity does not exist
Java Model Exception: Java Model Status [create-device-identity does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:137)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler.access$0(CodeLensHandler.java:134)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:59)
    at org.jboss.tools.vscode.java.internal.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:261)
    at org.jboss.tools.langs.base.LSPServer.lambda$1(LSPServer.java:212)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

Any idea what might cause this behaviour? Thanks!

[Question] Error in the console and output

--Sorry for the English, I used Google Translator --

If I have a project in Eclipse with the following project folders "Folder - EAR", "Folder - EJB", "Folder - WEB"), I can not use this extension?

I say this because when I set up the JAVA_HOME and installed the extension. I only open my "Folder - EJB" with vscode the first time and open a .java file. The extension began to download the necessary files and I indicated that everything was "ok - 👍 - . For vscode the file was in error the file, but for the Eclipse was not. So I closed the vscode and open again and shows me 👎 with the following message in the output:

[Error - 18:48:31] 11/10/2016 18:48:21 Problem importing to workspace
Invalid project description.
org.eclipse.core.internal.resources.ResourceException: Invalid project description.
at org.eclipse.core.internal.resources.Project.checkDescription(Project.java:169)
at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:53)
at org.eclipse.core.internal.resources.Project.create(Project.java:263)
at org.eclipse.core.internal.resources.Project.create(Project.java:247)
at org.jboss.tools.vscode.java.internal.managers.EclipseProjectImporter.createProject(EclipseProjectImporter.java:115)
at org.jboss.tools.vscode.java.internal.managers.EclipseProjectImporter.importToWorkspace(EclipseProjectImporter.java:85)
at org.jboss.tools.vscode.java.internal.managers.ProjectsManager.createProject(ProjectsManager.java:50)
at org.jboss.tools.vscode.java.internal.handlers.InitHandler$1.run(InitHandler.java:85)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Contains: OK
Contains: c:\FOLDER\Folder 1\test\FolderEJB overlaps the location of another project: 'FolderEJB'

And the console (Toggle Developer Tools) shows this:

shell.ts:428Illegal argument: Error: Illegal argument
at new e (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:9:24998)
at asHover (C:\Users\User \ .vscode\extensions\redhat.java-0.0.4\node_modules\vscode-languageclient\lib\protocolConverter.js:71:16)
at process._tickCallback (internal/process/next_tick.js:103:7)e.onUnexpectedError @ shell.ts:428
2shell.ts:428 Illegal argument: Error: Illegal argument
at new e (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:9:24998)
at asHover (C:\Users\User\ .vscode\extensions\redhat.java-0.0.4\node_modules\vscode-languageclient\lib\protocolConverter.js:71:16)
at process._tickCallback (internal/process/next_tick.js:103:7)e.onUnexpectedError @ shell.ts:428(anonymous function) @ shell.ts:341e.onUnexpectedError @ errors.ts:73u @ errors.ts:88(anonymous function) @ hover.ts:34m @ winjs.base.raw.js:1209B.enter @ winjs.base.raw.js:901n.Class.define._run @ winjs.base.raw.js:1068n.Class.define._error @ winjs.base.raw.js:1041m @ winjs.base.raw.js:1209B.enter @ winjs.base.raw.js:901n.Class.define._run @ winjs.base.raw.js:1068n.Class.define._error @ winjs.base.raw.js:1041(anonymous function) @ async.ts:358n.Class.define.done @ winjs.base.raw.js:1378m @ winjs.base.raw.js:1224B.enter @ winjs.base.raw.js:901n.Class.define._run @ winjs.base.raw.js:1068n.Class.define._error @ winjs.base.raw.js:1041e.resolveErr @ ipcRemoteCom.ts:110f @ ipcRemoteCom.ts:198_combinedTickCallback @ internal/process/next_tick.js:67_tickCallback @ internal/process/next_tick.js:98

and

shell.ts:428 Illegal argument: Error: Illegal argument
at new e (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:9:24998)
at asHover (C:\Users\User \ .vscode\extensions\redhat.java-0.0.4\node_modules\vscode-languageclient\lib\protocolConverter.js:71:16)
at process._tickCallback (internal/process/next_tick.js:103:7)e.onUnexpectedError @ shell.ts:428(anonymous function) @ shell.ts:341e.onUnexpectedError @ errors.ts:73u @ errors.ts:88(anonymous function) @ hover.ts:34m @ winjs.base.raw.js:1209B.enter @ winjs.base.raw.js:901n.Class.define._run @ winjs.base.raw.js:1068n.Class.define._error @ winjs.base.raw.js:1041m @ winjs.base.raw.js:1209B.enter @ winjs.base.raw.js:901n.Class.define._run @ winjs.base.raw.js:1068n.Class.define._error @ winjs.base.raw.js:1041(anonymous function) @ async.ts:358n.Class.define.done @ winjs.base.raw.js:1378m @ winjs.base.raw.js:1224B.enter @ winjs.base.raw.js:901n.Class.define._run @ winjs.base.raw.js:1068n.Class.define._error @ winjs.base.raw.js:1041e.resolveErr @ ipcRemoteCom.ts:110f @ ipcRemoteCom.ts:198_combinedTickCallback @ internal/process/next_tick.js:67_tickCallback @ internal/process/next_tick.js:98

I saw something about maven project on the README, the as I am starting programming, I still have no idea to work the same. Sorry for anything.

Issues downloading the additional extension files

I'm using 0.0.4. After I install the plugin I see the files appear in ~./vscode/extensions/redhat.java-0.0.4. However I don't see any files (other than .gitignore) in the .../server dir. VSCode shows "Java" but there's no thumbs up. Is there a log file that I can look at? (and there's a pom.xml file in the root which compiles with mvn).

Nothing more than syntax coloring

After installing this extension, I installed OpenJDK 1.8.0_102-1.redhat and set the JAVA_HOME environment variable. Java files load successfully and I have syntax coloring but nothing else! (e.g. code lens, code completion, ...).
Then, tried with 0.0.2 but no luck so I followed the troubleshooting section without any more luck.
Am I the only one to have this issue?
Windows 10 x64 Anniversary Edition.

PM Creating working copy empty does not exist

I am using vscode-java with selenium project.
After I cloned form https://github.com/SeleniumHQ/selenium.git,
I create 2 pom.xml files, one for /selenium/java/client, one for /selenium/java/server, as below.

pom.xml for client

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.seleniumhq</groupId>
  <artifactId>client</artifactId>
  <version>2.52.0</version>
  <build>
    <directory>${project.basedir}/build</directory>
    <outputDirectory>${project.build.directory}/production</outputDirectory>
    <sourceDirectory>src</sourceDirectory>
    <testSourceDirectory>test</testSourceDirectory>
  </build>
</project>

pom.xlm for server

<project>
  <parent>
    <groupId>org.seleniumhq</groupId>
    <artifactId>client</artifactId>
    <version>2.52.0</version>
    <relativePath>../client/pom.xml</relativePath>
  </parent>
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.seleniumhq</groupId>
  <artifactId>server</artifactId>
  <version>2.52.0</version>
  <build>
    <directory>${project.basedir}/build</directory>
    <outputDirectory>${project.build.directory}/production</outputDirectory>
    <sourceDirectory>src</sourceDirectory>
    <testSourceDirectory>test</testSourceDirectory>
  </build>
</project>

when I open a java file in the server project, everything works well,
but when I open a java file in the client project,
PM Problem encountered like below.

[Error] Sep 25, 2016 4:17:27 PM Creating working copy 
empty does not exist
Java Model Exception: Java Model Status [empty does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.Openable.getBuffer(Openable.java:285)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.handleOpen(DocumentLifeCycleHandler.java:142)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.access$1(DocumentLifeCycleHandler.java:126)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$OpenHandler$1.run(DocumentLifeCycleHandler.java:75)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$OpenHandler.handle(DocumentLifeCycleHandler.java:72)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$OpenHandler.handle(DocumentLifeCycleHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchNotification(LSPServer.java:222)
    at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:156)
    at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

[Error] Sep 25, 2016 4:17:27 PM Problem getting code lenses forFirefoxDriver.java
empty does not exist
Java Model Exception: Java Model Status [empty does not exist]
    at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
    at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1176)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
    at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
    at org.jboss.tools.vscode.java.handlers.CodeLensHandler.getCodeLensSymbols(CodeLensHandler.java:124)
    at org.jboss.tools.vscode.java.handlers.CodeLensHandler.access$0(CodeLensHandler.java:122)
    at org.jboss.tools.vscode.java.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:47)
    at org.jboss.tools.vscode.java.handlers.CodeLensHandler$CodeLensProvider.handle(CodeLensHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchRequest(LSPServer.java:210)
    at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:165)
    at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

What exactly do I have to install to make this work?

What does this mean? "Recognizes only projects with maven build files on the directory hierarchy, or to a lesser extent, simple Eclipse projects, i.e. containing .project and .classpath files." I am new to Java. What do I have to install on a freshly installed Windows 10 machine? What I already have is Visual Studio Code (latest version), a Java 8 SDK with JAVA_HOME set and the Redhat Java plugin. And a java file to look into it.

Label = question

Output fails with compilation error : PM Problem getting code lenses

I have successfully installed the extension:

  1. folder ~/.vscode/extensions/redhat.java-0.0.3/server is present
  2. The icon with "Thumbs up" is avalaible
  3. Im using maven project structure
    But whenever i perform any change, there is below stacktrace in output panel:

[Error] Sep 19, 2016 3:59:20 PM Problem with codeSelect forNumberFormatValidator.java t2si-api does not exist Java Model Exception: Java Model Status [t2si-api does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)

Im on linux, behind company proxy. Thanks in advance

isWatching not working

I have configured a task to test the application and wanted it to execute on file save, if I execute it through crtl+shift+p->run test task it works. tasks.json below:

{
"version": "0.1.0",
"command": "mvn",
"isShellCommand": true,
"showOutput": "always",
"suppressTaskName": true,
"tasks": [
{
"taskName": "test",
"isTestCommand": true,
"isWatching": true,
"args": [
"test"
]
}
]
}

Getting Error AM Exception on incoming message dispatcher

Everytime I type anything into the editor I get the following error in my Ouput log:

[Error] Sep 22, 2016 10:32:13 AM Exception on incoming message dispatcher
null
java.lang.NullPointerException
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.handleChanged(DocumentLifeCycleHandler.java:157)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.access$2(DocumentLifeCycleHandler.java:154)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler$1.run(DocumentLifeCycleHandler.java:98)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:95)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:1)
at org.jboss.tools.langs.base.LSPServer.dispatchNotification(LSPServer.java:222)
at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:156)
at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

OS: Windows 7 Enterprise x64 SP1
Visual Code Version: 1.5.2
JDK Version: 1.8.102 (Oracle)
Language Support version: 0.0.3

Failed to initialize the extension for the first run

When I first install the Java extension, and create a java file, the initialize started, but always failed with below messages:

[Error - 08:42:42] 2016-10-5 8:42:42 An internal error occurred during: "Initialize Workspace".
null
java.lang.NullPointerException
    at java.io.File.<init>(File.java:277)
    at org.jboss.tools.vscode.java.internal.managers.ProjectsManager.createProject(ProjectsManager.java:46)
    at org.jboss.tools.vscode.java.internal.handlers.InitHandler$1.run(InitHandler.java:85)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[Error - 08:42:42] Request textDocument/codeLens failed.
  Message: undefined
  Code: -32603

how to solve this problem?

Implement a fake server run mode

Create a fake run mode so that the java server can be started from within eclipse.
In this mode everything that is normally done will be created except the java server.

Option to specify Java path ?

The extension needs Java 8 and I'm working on Java 7 projects so I cannot updated to Java 8 easily.

How about an option to specify Java directory (JAVA_HOME already points to Java 7) ?

Would like to be able to recognise java files without maven too

Great initiative. I am using VS code more and more and tools like eclipse less and less. I think however, that this is a big limitation: "Recognizes only projects with maven build files on the directory hierarchy.".

Would love to be able to open any java file in code - even if ANT or some other build tool is used. It would be OK to remove some functionality if there is no recognised project for the java file but simple things like syntax highlighting and completion of calls into standard java packages should continue to work.

Language Support for Java(TM) by Red Hat - Couldn't start client Language Support for Java

Hi guys:

I just recently installed the Language Support for Java extension however, I can't seem to get it working. Whenever I open a Java file I get a message stating the it "Couldn't start client Language Support for Java".

I get an error output that reads:

[Error - 11:54:37 PM] Starting client failed
13

I've already checked to see if JAVA_HOME is mapped under Environment Variables and it has. Any help would be appreciated.
Thanks!
Alexander Tang

Add "add missing import" quick fix/action

In order to quickly fix missing imports when pasting code or writing code - it would be great to have a quick fix to "add import" similarly to e.g. the C# vscode extension or various Java IDEs

Exceptions are thrown when setting the Java type to a new file

It seems setting a new file language to java, before a workspace folder has been defined (i.e. not within an already opened Maven or Eclipse project), causes problems, as seen in See https://github.com/gorkem/vscode-java/issues/32#issuecomment-249031009

[Error] 22-sep-2016 23:17:02 Exception on incoming message dispatcher
null argument:
org.eclipse.core.runtime.AssertionFailedException: null argument:
    at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
    at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
    at org.eclipse.core.runtime.Path.initialize(Path.java:641)
    at org.eclipse.core.runtime.Path.<init>(Path.java:238)
    at org.eclipse.core.runtime.Path.<init>(Path.java:186)
    at org.eclipse.core.runtime.Path.fromOSString(Path.java:92)
    at org.jboss.tools.vscode.java.handlers.AbstractRequestHandler.resolveCompilationUnit(AbstractRequestHandler.java:33)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.handleOpen(DocumentLifeCycleHandler.java:127)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.access$1(DocumentLifeCycleHandler.java:126)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$OpenHandler$1.run(DocumentLifeCycleHandler.java:75)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$OpenHandler.handle(DocumentLifeCycleHandler.java:72)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$OpenHandler.handle(DocumentLifeCycleHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchNotification(LSPServer.java:222)
    at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:156)
    at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

[Error] 22-sep-2016 23:17:02 Exception on incoming message dispatcher
null argument:
org.eclipse.core.runtime.AssertionFailedException: null argument:
    at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
    at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
    at org.eclipse.core.runtime.Path.initialize(Path.java:641)
    at org.eclipse.core.runtime.Path.<init>(Path.java:238)
    at org.eclipse.core.runtime.Path.<init>(Path.java:186)
    at org.eclipse.core.runtime.Path.fromOSString(Path.java:92)
    at org.jboss.tools.vscode.java.handlers.AbstractRequestHandler.resolveCompilationUnit(AbstractRequestHandler.java:33)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.handleChanged(DocumentLifeCycleHandler.java:155)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.access$2(DocumentLifeCycleHandler.java:154)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler$1.run(DocumentLifeCycleHandler.java:98)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:95)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchNotification(LSPServer.java:222)
    at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:156)
    at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

[Error] 22-sep-2016 23:17:02 Exception on incoming message dispatcher
null argument:
org.eclipse.core.runtime.AssertionFailedException: null argument:
    at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
    at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
    at org.eclipse.core.runtime.Path.initialize(Path.java:641)
    at org.eclipse.core.runtime.Path.<init>(Path.java:238)
    at org.eclipse.core.runtime.Path.<init>(Path.java:186)
    at org.eclipse.core.runtime.Path.fromOSString(Path.java:92)
    at org.jboss.tools.vscode.java.handlers.AbstractRequestHandler.resolveCompilationUnit(AbstractRequestHandler.java:33)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.handleChanged(DocumentLifeCycleHandler.java:155)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.access$2(DocumentLifeCycleHandler.java:154)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler$1.run(DocumentLifeCycleHandler.java:98)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:95)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchNotification(LSPServer.java:222)
    at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:156)
    at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

Ver 0.0.3 - java.lang.NullPointerException - (DocumentLifeCycleHandler.java:157) 

[Error] 2016-9-26 19:46:10 Exception on incoming message dispatcher
null
java.lang.NullPointerException
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.handleChanged(DocumentLifeCycleHandler.java:157)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.access$2(DocumentLifeCycleHandler.java:154)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler$1.run(DocumentLifeCycleHandler.java:98)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:95)
    at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:1)
    at org.jboss.tools.langs.base.LSPServer.dispatchNotification(LSPServer.java:222)
    at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:156)
    at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

Above is the full error log, and i am using Window 10. That`s all.

In addition, i cannot see the thumbs up.

Error in the console - response has neither result nor error

[Error - 8:14:38 AM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
at handleInvalidMessage (/Users/navneet/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
at StreamMessageReader.callback (/Users/navneet/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
at StreamMessageReader.onData (/Users/navneet/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
at Socket. (/Users/navneet/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
at emitOne (events.js:90:13)
at Socket.emit (events.js:182:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at Pipe.onread (net.js:531:20)

Unit tests inside src/test/java are not being recognized

My Maven project has some test classes and using this plugin it is showing a lot of errors. One of them is the below:

"The declared package br.nom.martinelli.ricardo.academix does not match the expected package src.text.java.br.nom.martinelli.ricardo.academix" (1,9)

Which IMO means that the plugin didn't recognize src/test/java as the test dir for my maven project.

Download requirement fails (with http error 503)

I am using VSC behind a proxy and plugin is not able to download dependencies.

It fails because Server Url is a http, and downloadManager use https agent without setting the options.port to the correct port.
agent-base set port to 443, when options.port is omitted. Request fail because resource is unavailable at this new location.

doesn't work on macOS

Java 8 is installed, but can't be recognized. Links to RedHat's OpenJDK, but it has no macOS version as well.

.class file not colored

Use goto definition and navigate to a compiled file (for example Click on "String" type) and see the String.class file. it doesn't recognized as Java.

Error: self signed certificate in certificate chain

I am behind a corporate firewall, when the extension starts it fails to download the required parts with the following "Error: self signed certificate in certificate chain". I have the correct proxy settings and "http.proxyStrictSSL": false. VS Code updates and the marketplace are working fine.

Do you have any suggestions?

Thanks

java.lang.NullPointerException v0.0.3

I just download the plugging (fresh Visual Studio) using Ubuntu 16.04

Visual Studio from (code_1.5.2-1473686317_amd64.deb)

[Error] Sep 22, 2016 10:19:08 AM Exception on incoming message dispatcher
null
java.lang.NullPointerException
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.handleChanged(DocumentLifeCycleHandler.java:157)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler.access$2(DocumentLifeCycleHandler.java:154)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler$1.run(DocumentLifeCycleHandler.java:98)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:95)
at org.jboss.tools.vscode.java.handlers.DocumentLifeCycleHandler$ChangeHandler.handle(DocumentLifeCycleHandler.java:1)
at org.jboss.tools.langs.base.LSPServer.dispatchNotification(LSPServer.java:222)
at org.jboss.tools.langs.base.LSPServer.messageReceived(LSPServer.java:156)
at org.jboss.tools.langs.transport.AbstractConnection$DispatcherThread.run(AbstractConnection.java:32)

Need to add a visual clue when starting the JLS

when the extension kicks in, the JLS provide feedback only starting from when the JVM has started.
There's a few seconds during which we have 0 indication something is happening, which can be pretty confusing. The tray should display "Starting Java Language Server..." (or better), before the Initialization notifications kick in.

error message on console

on MAC OSX,

the version is the newest version from vscode ,and vscode is the newest release from vscode(downloaded today)(1.5.3).

node version is v6.7.0

mac version is sierra

how ever, the console shows these log time after time

[Error - 6:20:53 PM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
    at handleInvalidMessage (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
    at StreamMessageReader.callback (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
    at StreamMessageReader.onData (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
    at Socket.<anonymous> (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:531:20)
[Error - 6:21:59 PM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
    at handleInvalidMessage (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
    at StreamMessageReader.callback (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
    at StreamMessageReader.onData (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
    at Socket.<anonymous> (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:531:20)
[Error - 6:22:03 PM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
    at handleInvalidMessage (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
    at StreamMessageReader.callback (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
    at StreamMessageReader.onData (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
    at Socket.<anonymous> (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:531:20)
[Error - 6:22:04 PM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
    at handleInvalidMessage (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
    at StreamMessageReader.callback (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
    at StreamMessageReader.onData (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
    at Socket.<anonymous> (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:531:20)
[Error - 6:22:50 PM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
    at handleInvalidMessage (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
    at StreamMessageReader.callback (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
    at StreamMessageReader.onData (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
    at Socket.<anonymous> (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:531:20)
[Error - 6:28:35 PM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
    at handleInvalidMessage (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
    at StreamMessageReader.callback (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
    at StreamMessageReader.onData (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
    at Socket.<anonymous> (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:531:20)
[Error - 6:30:26 PM] Request textDocument/definition failed.
Error: The received response has neither a result nor an error property.
    at handleInvalidMessage (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:294:40)
    at StreamMessageReader.callback (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/main.js:366:13)
    at StreamMessageReader.onData (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:197:18)
    at Socket.<anonymous> (/Users/mudu/.vscode/extensions/redhat.java-0.0.4/node_modules/vscode-languageclient/node_modules/vscode-jsonrpc/lib/messageReader.js:164:19)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:531:20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.