I wonder, would it be possible to reuse language server processes, for example if I open directory in Code, start editing application.properties (with completion) and then decided to open project in Eclipse IDE.

For reference Gradle would reuse daemon process if the same version is used in command line and IDE.

I get the following error:
Error trying to find JVM: Unexpected output from java -XshowSettings:properties. Didn't find all expected properties: java.version,java.home

I suspect this is because in my env var I have set JAVA_HOME to JDK 6. Unfortunately I won't be able to change that.
I do have JDK 8 installed which is referenced through java.home VSCode settings for/by another plugin. Can you please add similar or reuse same setting to support configurable JDK?

P2 URL link doesn't seem to work with Eclipse-Photon.

The link in the wiki (https://github.com/spring-projects/sts4/wiki/Installation), namely http://download.springsource.com/release/TOOLS/sts4/update/latest/ , doesn't work.

-Start fresh install of sts4 beta
-Create a demo project (similar to https://spring.io/blog/2017/12/04/spring-tips-spring-tool-suite-4)
-Open DemoApplication.java
-Ctrl-click on an annotation, (or press ctrl-6)
-Eclipse hangs for around a minute, then nothing happens.

This is the main thread stacktrace during that time:
java.util.concurrent.locks.LockSupport.parkNanos line: 215 java.util.concurrent.CompletableFuture$Signaller.block line: 1695 java.util.concurrent.ForkJoinPool.managedBlock line: 3323 java.util.concurrent.CompletableFuture.timedGet line: 1775 java.util.concurrent.CompletableFuture.get line: 1915 org.eclipse.lsp4e.LanguageServerWrapper.getServerCapabilities line: 488 org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers line: 243 org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor line: 354 org.eclipse.lsp4e.operations.documentLink.DocumentLinkDetector.detectHyperlinks line: 86 org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks line: 78 org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks line: 286 org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks line: 259 org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove line: 454 org.eclipse.swt.widgets.TypedListener.handleEvent line: 213 org.eclipse.swt.widgets.EventTable.sendEvent line: 86 org.eclipse.swt.widgets.Display.sendEvent line: 4428 org.eclipse.swt.widgets.Widget.sendEvent line: 1079 org.eclipse.swt.widgets.Display.runDeferredEvents line: 4238 org.eclipse.swt.widgets.Display.readAndDispatch line: 3817

I also noted that when opening sts, a long time (several minutes) was spent on "Initialize Languague Server For DemoApplication". Stacktrace:

sun.misc.Unsafe.park line: not available [native method] java.util.concurrent.locks.LockSupport.park line: 175 java.util.concurrent.CompletableFuture$Signaller.block line: 1693 java.util.concurrent.ForkJoinPool.managedBlock line: 3323 java.util.concurrent.CompletableFuture.waitingGet line: 1729 java.util.concurrent.CompletableFuture.join line: 1934 org.eclipse.lsp4e.LanguageServerWrapper.getServer line: 445 org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor line: 357 org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run line: 74 org.eclipse.core.internal.jobs.Worker.run line: 56

When running a Spring Boot project ($ mvn spring-boot:run) in Linux subsystem in windows 10 (WSL bash shell, Ubuntu 16.04 distro), Boot Hints does not show up.

There are no warnings nor errors that I could see in the output box for the Spring Boot Tool VSCode extension (Pivotal.vscode-spring-boot).

Boot Hints show up normally if I run a Spring Boot project in git bash for windows 10, or in cmd on the same computer.

It's nice to get the documentation in application.properties, but I don't see a way to jump to the source code (like you can in STS3). Am I missing something?

On importing a fresh project, I get the a popup with the message:

Your IDE is missing natures to properly support your projects.
Some extensions on the eclipse marketplace can be installed to support those natures.

Clicking on show solution opens the eclipse marketplace and shows Spring Tool Suite 3.9.3 plugin for installation.

In Problems, the following warning shows up:
Description Resource Path Location
Type Unknown referenced nature: org.springframework.ide.eclipse.core.springnature.
.project /PROJECT_NAME Unknown Unknown nature

I imported the project cleanly. Only items in the project were src and .git folder and pom file.

I now tried to use the Language Server feature with a more complex example. The example project is part of a bigger Gradle multi-project build and in the Eclipse workspace there are also some unused pom.xml files (we migrated to Gradle recently). If I start Eclipse I get Spring Boot Java Language Server Error "Cannot load Gradle project model from folder: ...". Sometimes I also get the error "Cannot load Maven project model ..." where it picks a (random?) pom.xml file from my Eclipse workspace. I'm wondering what STS4/Language Server expects here. Does it really try to load my build files? The Eclipse projects itself doen't have any Maven/Gradle nature. We just generate Eclipse project files from Gradle and import them as normal Java Projects. Does STS4 require to have Gradle/Maven Eclipse projects or should it also work with "plain" Java projects?

In the Eclipse workspace log I get the following error but I'm not sure if it's related:

!ENTRY org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer 4 1000 2017-12-12 11:13:56.774
!MESSAGE Missing header Content-Length in input "
"
!STACK 0
java.lang.IllegalStateException: Missing header Content-Length in input "
"
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:73)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:84)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)

Should I create a new issue for this problem?

Thanks and regards,
Andreas

In the current version of STS4 in Eclipse there's no Spring Perspective nor Spring Explorer... will they be added back in the future?

Error messages " No Suggestions " when I type "spr..and ctrl + space" in application.yml

My environment:

• VSCode : 1.23.1 on MAC(High Sierra 10.13.4)

• JDK

  • java version "9.0.4"
  • Java(TM) SE Runtime Environment (build 9.0.4+11)
  • Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)

• Extension

  • Pivotal.vscode-boot-dev-pack
  • Pivotal.vscode-concourse
  • Pivotal.vscode-manifest-yaml
  • Pivotal.vscode-spring-boot
  • redhat.java
  • vscjava.vscode-java-debug
  • vscjava.vscode-java-pack
  • vscjava.vscode-java-test
  • vscjava.vscode-maven
  • vscjava.vscode-spring-initializr

• User Settings:
  {
  "git.enableSmartCommit": true,
  "git.autofetch": true,
  "git.confirmSync": false,
  "editor.renderWhitespace": "all",
  "window.zoomLevel": 0,
  "editor.wordWrap": "on",
  "workbench.sideBar.location": "left",
  "java.errors.incompleteClasspath.severity": "error",
  "files.associations": {
  "application*.yml": "spring-boot-properties-yaml",
  "application.yml": "spring-boot-properties-yaml",
  "ap of plication*.properties": "spring-boot-properties"
  }
  }

-Output of vscode-spring-boot-debug

Activating 'vscode-spring-boot' extension
Found java exe: /Library/Java/JavaVirtualMachines/jdk-9.0.4.jdk/Contents/Home/bin/java
isJavaEightOrHigher => true
Redirecting server logs to /var/folders/5l/4481t0p560l59p41d5jnc2pm0000gn/T/vscode-spring-boot-1528105318722.log
ERR: Redirecting log output to: /var/folders/5l/4481t0p560l59p41d5jnc2pm0000gn/T/vscode-spring-boot-1528105318722.log

Child process connected on port 45556

• logfile

[main] INFO org.springframework.ide.vscode.commons.util.Log - Starting LS
[main] INFO org.springframework.ide.vscode.commons.util.Log - Connected to parent using socket on port 45556
[pool-3-thread-1] INFO org.springframework.ide.vscode.commons.util.Log - Settings received: {"boot-java":{"boot-hints":{"on":true}}}
[STS4 Thread-1] INFO org.springframework.ide.vscode.commons.boot.app.cli.SpringBootApp - SpringBootApp created: Process [id=4122, name=`/Users/seungil/.vscode/extensions/redhat.java-0.26.0/server/plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar -configuration /Users/seungil/.vscode/extensions/redhat.java-0.26.0/server/config_mac -data /Users/seungil/Library/Application Support/Code/User/workspaceStorage/7c65af938e80727fa6060f215d94b870/redhat.java/jdt_ws`]
[STS4 Thread-1] INFO org.springframework.ide.vscode.commons.boot.app.cli.SpringBootApp - SpringBootApp created: Process [id=3756, name=`/Users/seungil/.vscode/extensions/Pivotal.vscode-spring-boot-0.2.1/jars/spring-boot-language-server-0.2.1-SNAPSHOT.jar`]
[STS4 Thread-1] INFO org.springframework.ide.vscode.commons.boot.app.cli.SpringBootApp - SpringBootApp created: Process [id=4127, name=`org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.3`]
[STS4 Thread-1] INFO org.springframework.ide.vscode.boot.jdt.ls.JdtLsProjectCache - Project Created: file:/Users/seungil/Library/Application%20Support/Code/User/workspaceStorage/7c65af938e80727fa6060f215d94b870/redhat.java/jdt_ws/jdt.ls-java-project
[STS4 Thread-1] INFO org.springframework.ide.vscode.boot.jdt.ls.JdtLsProjectCache - Classpath has 2 entries
[pool-3-thread-1] INFO org.springframework.ide.vscode.commons.util.Log - Settings received: {"boot-java":{"boot-hints":{"on":true}}}
[pool-3-thread-1] INFO org.springframework.ide.vscode.commons.util.Log - Settings received: {"boot-java":{"boot-hints":{"on":true}}}
[STS4 Thread-1] WARN org.springframework.ide.vscode.commons.util.Log - Change event with bad version ignored
[STS4 Thread-1] WARN org.springframework.ide.vscode.commons.util.Log - Change event with bad version ignored
[STS4 Thread-1] WARN org.springframework.ide.vscode.commons.util.Log - Change event with bad version ignored
[STS4 Thread-1] WARN org.springframework.ide.vscode.commons.util.Log - Change event with bad version ignored
[STS4 Thread-1] WARN org.springframework.ide.vscode.commons.util.Log - Change event with bad version ignored

I tried delete all of extension and reinstall them but I couldn't get autocomplete list.
I really like and want this function. Is there any way to fix this?

Hello, it seems that lombok is unable to recognize STS4 as an IDE. Any thoughts?

See related discussion here: #24

Concourse CI Pipeline Editor: Version: 0.0.9-RC.4
VS Code: v1.17.2
OS: Mac

I set the array in _vars.yml as below:

...
DOCKER_INSECURE_REGISTRIES: [ "10.244.0.8:443" ]

And use it in pipeline.yml like:

resources:
- name: image-XXX
  type: docker-image
  source:
    repository: ((DOCKER_IMAGE))
    insecure_registries: ((DOCKER_INSECURE_REGISTRIES))
    tag: latest

But this plugin will complain: Expecting a 'Sequence' but found a 'Scala'
After I disabled this plugin, the validation error would be disappeared so it's really caused by it.

There have been some iterations to the resources in the current release of concourse. Git resources now has a clean_tags param as an example. How do we update the validation inside the extension to account for this. Right now I have a bunch of "errors" in my pipeline files because we're using these new parameters that aren't accounted for.

I like the CTRL-T > feature, but it only seems to work for @Beans (not for Functions in a @FunctionScan or @ComponentScan).

I'm just running a basic sample app from start.spring.io in STS4.

Error occurred during initialization of boot layer
java.lang.LayerInstantiationException: Package jdk.internal.jimage.decompressor in both module java.base and module jrt.fs

jrt-fs.jar is the name of the 1 jar in the JDK library for Java 9

anchor &
reference *
extend <<

Due to the changes in how Spring boot actuator endpoints work sts4 cannot find the information it needs to provide runtime feedback such as the available endpoints in your application or simply the classes that are loaded at runtime...

It's great to use Spring Boot for the LSP, but launching from the JarLauncher is a problem because you can't tell what the process is doing from jps.

Boot hint breaks with the following error in the log:

[Timer-0] ERROR org.springframework.ide.vscode.commons.util.Log - Error
org.json.JSONException: JSONObject["contexts"] not found.
	at org.json.JSONObject.get(JSONObject.java:471)
	at org.json.JSONObject.getJSONObject(JSONObject.java:636)
	at org.springframework.ide.vscode.commons.boot.app.cli.requestmappings.RequestMappingsParser20.parse(RequestMappingsParser20.java:23)
	at org.springframework.ide.vscode.commons.boot.app.cli.SpringBootApp.parseRequestMappingsJson(SpringBootApp.java:202)
	at org.springframework.ide.vscode.commons.boot.app.cli.SpringBootApp.getRequestMappings(SpringBootApp.java:227)
	at org.springframework.ide.vscode.boot.java.requestmapping.RequestMappingHoverProvider.getRequestMappingMethodFromRunningApp(RequestMappingHoverProvider.java:106)
	at org.springframework.ide.vscode.boot.java.requestmapping.RequestMappingHoverProvider.getLiveHoverHints(RequestMappingHoverProvider.java:61)
	at org.springframework.ide.vscode.boot.java.handlers.BootJavaHoverProvider.lambda$extractLiveHintsForAnnotation$2(BootJavaHoverProvider.java:170)
	at java.base/java.util.Optional.ifPresent(Optional.java:175)
	at org.springframework.ide.vscode.boot.java.handlers.BootJavaHoverProvider.extractLiveHintsForAnnotation(BootJavaHoverProvider.java:168)
	at org.springframework.ide.vscode.boot.java.handlers.BootJavaHoverProvider$1.visit(BootJavaHoverProvider.java:106)
	at org.eclipse.jdt.core.dom.SingleMemberAnnotation.accept0(SingleMemberAnnotation.java:162)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2796)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2867)
	at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:618)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2796)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2867)
	at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:470)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2796)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2867)
	at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:257)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2796)
	at org.springframework.ide.vscode.boot.java.handlers.BootJavaHoverProvider.lambda$getLiveHoverHints$0(BootJavaHoverProvider.java:90)
	at org.springframework.ide.vscode.boot.java.utils.CompilationUnitCache.withCompilationUnit(CompilationUnitCache.java:113)
	at org.springframework.ide.vscode.boot.java.handlers.BootJavaHoverProvider.getLiveHoverHints(BootJavaHoverProvider.java:86)
	at org.springframework.ide.vscode.boot.java.utils.SpringLiveHoverWatchdog.update(SpringLiveHoverWatchdog.java:151)
	at org.springframework.ide.vscode.boot.java.utils.SpringLiveHoverWatchdog.update(SpringLiveHoverWatchdog.java:170)
	at org.springframework.ide.vscode.boot.java.utils.SpringLiveHoverWatchdog$2.run(SpringLiveHoverWatchdog.java:108)
	at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
	at java.base/java.util.TimerThread.run(Timer.java:506)

Boot hint in older version of Pivotal.vscode-boot-java plugin works.

I have tried to delete the tmp folder hsperf- as the wiki suggests for when Boot Hint does not show up. It didn't do it.

Environment

• Operating System: windows 10
• JDK version: 1.8.0_131
• Visual Studio Code version: 1.19.3

We have an application that sets the default JMX domain to our company prefix "com.build". Since STS4 is using JMX to provide the live hover support, it does not find any of the actuator endpoints because they are under a different domain. I am not sure you can detect the domain on startup (probably not), so this might just be a configuration property that is added to the tool: "Actuator JMX Domain" or maybe just something that is added to the documentation.

I was able to work around the problem by setting the "endpoints.jmx.domain" back to "org.springframework.boot".

I have added the Spring Boot Extension Pack with the extensions tab inside Visual Studio Code. For the Live application information hovers I have to add the workspace setting "boot-java.boot-hints.on", but it remains unknown for the IDE.

I have also installed the "Java Extension Pack"

Error on start up:

JAVA_HOME environment variable points either to JRE or JDK missing "lib/tools.jar" hence Boot Hints are unavailable

Boot Hint works if I copy "lib/tools.jar" from older java jdk version to jdk-9.0.1/ folder.

I am using STS4 in Win10 and have few gradle and maven projects in my workspace.
Getting below exceptions in workspace log and its causing horrible slowness while working with Tool4.

I could not able to disable 'Language Servers' using preferences.

Are there any settings available to STS4, to fix this issue?

eclipse.buildId=4.0.0.201711271125-M6
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.springframework.boot.ide.branding.sts4
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.springframework.boot.ide.branding.sts4

!ENTRY org.eclipse.lsp4e 4 0 2017-12-11 23:41:48.162
!MESSAGE java.util.concurrent.CancellationException
!STACK 0
java.util.concurrent.CompletionException: java.util.concurrent.CancellationException
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
	at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:593)
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
	at java.util.concurrent.CompletableFuture.cancel(CompletableFuture.java:2265)
	at org.eclipse.lsp4e.LanguageServerWrapper.stop(LanguageServerWrapper.java:283)
	at org.eclipse.lsp4e.LanguageServerWrapper.start(LanguageServerWrapper.java:169)
	at org.eclipse.lsp4e.LanguageServerWrapper.getInitializedServer(LanguageServerWrapper.java:457)
	at org.eclipse.lsp4e.LanguageServerWrapper.getServerCapabilities(LanguageServerWrapper.java:488)
	at org.eclipse.lsp4e.LanguageServiceAccessor.lambda$4(LanguageServiceAccessor.java:312)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
	at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1548)
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
	at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getMatchingStartedWrappers(LanguageServiceAccessor.java:313)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:221)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:354)
	at org.eclipse.lsp4e.operations.declaration.OpenDeclarationHyperlinkDetector.detectHyperlinks(OpenDeclarationHyperlinkDetector.java:77)
	at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:78)
	at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:286)
	at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:259)
	at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:454)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:213)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
Caused by: java.util.concurrent.CancellationException
	at java.util.concurrent.CompletableFuture.cancel(CompletableFuture.java:2263)
	... 49 more

!ENTRY org.eclipse.lsp4e 4 0 2017-12-11 23:41:58.184
!MESSAGE LanguageServer not initialized after 10s
!STACK 0
java.util.concurrent.TimeoutException
	at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1771)
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
	at org.eclipse.lsp4e.LanguageServerWrapper.getServerCapabilities(LanguageServerWrapper.java:488)
	at org.eclipse.lsp4e.LanguageServiceAccessor.lambda$4(LanguageServiceAccessor.java:312)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
	at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1548)
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
	at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getMatchingStartedWrappers(LanguageServiceAccessor.java:313)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:221)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:354)
	at org.eclipse.lsp4e.operations.declaration.OpenDeclarationHyperlinkDetector.detectHyperlinks(OpenDeclarationHyperlinkDetector.java:77)
	at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:78)
	at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:286)
	at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:259)
	at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:454)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:213)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1472)

For some steps that demonstrate how unreliable it is... see: microsoft/vscode-spring-boot-dashboard#15

Hi,

When working on a concourse configuration in VSCode with the concourse extension installed, when I added a tag to a resource in the form

resources:
  - name: abc
    tag: [test]

"tag" is underlined with the error stating

unknown property 'tag' for type 'Resource'

I think this is a newer feature to concourse added in responce to this issue, closed in March 2017 with the feature now available as described here.

Thanks

What are features supported by idea-extensions/idea-boot-java ? And any planned development on this extension for future ?

Hi,

I have the following resource defined in my pipeline:

resources:
- name: resource-name
  type: semver
  check_every: 1h  
  source:
    driver: gcs
    bucket: bucket-name
    key: version
    json_key: ((gcp.key))

This works fine in Concourse, but the VScode plugin shows the following problems:

'gcs' is an unknown 'SemverDriver'. Valid values are: [git, s3, swift]
Unknown property 'bucket' for type 'SemverSource'
Unknown property 'key' for type 'SemverSource'
Unknown property 'json_key' for type 'SemverSource'

Can this support be enabled? It is documented here: https://github.com/concourse/semver-resource

@kdvolder as you mentioned in #64 I have a list of two more missing params.

git-resource - put - params - merge: Unknown property 'merge' for type 'GitPutParams'

pipeline job - plan - task - on_abort: Unknown property 'on_abort' for type 'TaskStep'

I believe in combination with the others you noted in #64 are all the missing items I've encountered. Thanks so much for helping with this.

as mentioned in comment #30 (comment), people observed a slowness when running the boot-java extension on JDK9. We need to investigate this.

Any way to use https://marketplace.visualstudio.com/items?itemName=patrys.vscode-code-outline to have a outline like one has in atom?

I am aware of lookup symbols and thats already great, but having the whole tree to explore is something very useful.

Extremely valuable plugin overall, thank you very much!

i am sorry that i don't know why it works well sometimes(for a few times), but not always? it must connect to the internet?

Greetings,

Need you knowledge to help address the issue raised in VSCode Java Debugger Extension. Could you share some thoughts about the fix?

microsoft/vscode-java-debug#157

Thanks!

Hi,

I just wanted to try out the new STS4 beta version with a simple Spring Boot Demo project. But when starting Eclipse STS4 I always get the following error in the Eclipse Error Log:

LanguageServer not initialized after 10s

with the following stack trace:

java.util.concurrent.TimeoutException
	at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1771)
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
	at org.eclipse.lsp4e.LanguageServerWrapper.getServerCapabilities(LanguageServerWrapper.java:488)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:243)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:354)
	at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

And in the progress window the "Initialize Language Servers for DemoApplication.java" task hangs forever.

For installation I downloaded the "Spring Tools 4 for Eclipse" distribution and created an empty workspace without any additional customization:

Spring Tool Suite 4

Version: 4.0.0.M6
Build Id: 201711271125

My Eclipse is started with :

java.version=1.8.0_121
java.home=D:<JDK_HOME>\jre

If I understand it correctly Eclipse should start the Spring Boot Language Server but I guess this somehow fails. But I have no idea why or where I should look for further information. In the Eclipse workspace log I only see these log messages:

!ENTRY org.eclipse.ui 2 0 2017-12-11 12:52:33.022
!MESSAGE Warnings while parsing the images from the 'org.eclipse.ui.commandImages' extension point.
!SUBENTRY 1 org.eclipse.ui 2 0 2017-12-11 12:52:33.022
!MESSAGE Cannot bind to an undefined command: plug-in='org.eclipse.lsp4e', id='org.eclipse.lsp4e.togglehighlight'

!ENTRY org.eclipse.jface 2 0 2017-12-11 12:52:34.116
!MESSAGE Keybinding conflicts occurred.  They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2017-12-11 12:52:34.116
!MESSAGE A conflict occurred for CTRL+SHIFT+T:
Binding(CTRL+SHIFT+T,
	ParameterizedCommand(Command(org.eclipse.jdt.ui.navigate.open.type,Open Type,
		Open a type in a Java editor,
		Category(org.eclipse.ui.category.navigate,Navigate,null,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a7ae340,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)
Binding(CTRL+SHIFT+T,
	ParameterizedCommand(Command(org.eclipse.lsp4e.symbolinworkspace,Go to Symbol in Workspace,
		,
		Category(org.eclipse.lsp4e.category,Language Servers,null,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5e8bd498,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)

!ENTRY org.eclipse.lsp4e 4 0 2017-12-11 12:52:48.050
!MESSAGE LanguageServer not initialized after 10s
!STACK 0
java.util.concurrent.TimeoutException
	at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1771)
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
	at org.eclipse.lsp4e.LanguageServerWrapper.getServerCapabilities(LanguageServerWrapper.java:488)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:243)
	at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:354)
	at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

Any help is highly appreciated. The new "Runtime information in your editor" features looks really cool and I can't wait to try it out on my machine :-)

Thanks and regards,
Andreas

Hi!

I've seen this plug-in report lines that are valid pipeline config. What's interesting is that these pipelines are validating and formatted using fly format-pipeline so they should be totally legit.

pipeline.yml:

Both errors I have found were in the same inline task definition:

- task: find-ami
  config:
    platform: linux
    image_resource:
      type: docker-image
      source:
        repository: czero/rootfs
    params:
      REGION: ""
    run:
      path: bash
      args:
      - -c
      - |
        ami=$(grep $REGION pivnet-opsmgr/*.yml | cut -d' ' -f2)
        echo $ami > stock-ami/ami
    inputs:
    - name: pivnet-opsmgr
      path: ""
      optional: false
    outputs:
    - name: stock-ami
      path: ""
  params:
    REGION: {{aws_region}}

Errors:

1. here, the plugin complains the the paths in the input/output sections should not be empty, even though it was set to an empty string by fly format-pipeline and it is totally valid to do so (if the sting is empty, the name of the input/output is assumed to be the path)

2. here, the plugin complains about the new 'optional' property introduced in 3.9.0, see https://concourse.ci/running-tasks.html#input-optional

3. is the same as 1

let me know if you need more information!

When all dependencies are removed/unchecked from a boot project. The edit starters tends to create a broken project because it does not ensure that at leats a dependency like:

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter</artifactId>
</dependency>

Steps to reproduce:

1. create a project with "new Spring starter". Select a single dependency (e.g. web).
2. Use "Edit starters" and remove the dependency.

=> The dependency is removed from the pom leaving no dependencies in the pom at all.

The project is now broken and has compile errors.

Expected behavior is that upon removal of the last dependency we ensure that at least a dependency on
the 'base' spring-boot-starter dependency exists. If it doesn't it should be added.

Unknown property 'additional_tags' for type 'DockerImagePutParams'

The support of builtin resources needs to be updated.

I miss an option to export / import the configs of boot dashboard. This is very useful when you need to configure projects on other computers.

Unknown property 'routes' for type 'Application'

routes:
- route: api.mydomain.com

Assigning custom properties to a marker when creating/copying it is
deprecated. Please, consider storing the custom properties you need in
some other object in your package, keyed by the marker's id property.

Function.extractParams (<embedded>:79352:20)
MarkerLayer.markRange (<embedded>:80007:77)
DisplayMarkerLayer.markBufferRange (<embedded>:135609:58)
TextEditor.markBufferRange (<embedded>:4618:42)
BootStsAdapter.createHintMarker (/home/axpira/.atom/packages/spring-boot/build/boot-sts-adapter.js:31:31)
ranges.forEach.range (/home/axpira/.atom/packages/spring-boot/build/boot-sts-adapter.js:17:42)

I don't seem to see any "magic" in VSCode for application.yml. Am I missing something?

I have configured java.home property to point to JDK8 which tools.jar resided in lib folder but still get this warning.

After I install the Spring Boot Java Support for VS Code i get the following error (when opening a .java file):

JAVA_HOME environment variable points either to JRE or JDK missing "lib/tools.jar" hence Boot Hints are unavailable

echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home

The environment variable is well defined(see image) and recognised by following extensions without issues the:
Language Support for Java(TM) by Red Hat
Java Debugger by Microsoft

Probably I miss something else but the message is misleading - what are Boot Hints ?

VS Code 1.18.1
MacOS High Sierra

Export WAR option is required for Spring Web Projects to Deploy in Tomcat Server. It is missing in Version 4.

The Concourse CI Pipeline Editor plugin seems to try and take over validation of any file that happens to be named in the format of Tasks.yml. For example I had a file named NetCore-Tasks.yml and red squiggly lines were displayed in the editor. The documentation for the plugin states it should only match /tasks/.yml which seems reasonable given the concourse pipeline structure.

[2018-06-08 12:31:12.451] [renderer3] [error] Cannot read property 'selection' of undefined: TypeError: Cannot read property 'selection' of undefined
at CursorExploder.explode (C:\Users\wenlong.vscode\extensions\hoovercj.vscode-power-mode-2.2.0\out\src\cursor-exploder\cursor-exploder.js:145:66)
at CursorExploder.onDidChangeTextDocument (C:\Users\wenlong.vscode\extensions\hoovercj.vscode-power-mode-2.2.0\out\src\cursor-exploder\cursor-exploder.js:41:18)
at plugins.forEach.plugin (C:\Users\wenlong.vscode\extensions\hoovercj.vscode-power-mode-2.2.0\out\src\extension.js:119:38)
at Array.forEach (native)
at onDidChangeTextDocument (C:\Users\wenlong.vscode\extensions\hoovercj.vscode-power-mode-2.2.0\out\src\extension.js:119:13)
at e.fire (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:96:764)
at e.$acceptModelChanged (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:686:189)
at e._doInvokeHandler (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:636:832)
at e._invokeHandler (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:636:550)
at e._receiveRequest (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:635:631)
at e._receiveOneMessage (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:635:400)
at e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:634:315
at e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:637:395
at e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:95:432
at e.fire (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:96:764)
at Socket. (e:\ide\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:154:338)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at readableAddChunk (_stream_readable.js:178:18)
at Socket.Readable.push (_stream_readable.js:136:10)
at Pipe.onread (net.js:560:20)

From release v1.26, defining an Extension Pack now uses a new property called extensionPack instead of extensionDependencies in package.json. This is because extensionDependencies is mainly used to define functional dependencies and an Extension Pack should not have any functional dependencies with its bundled extensions and they should be manageable independent of the pack.

So please use extensionPack property for defining the pack.

For more details refer to Release notes

This extension is categorised as extension pack and hence this issue is filed. If you think this does not impact the extension, please close it.

Hi,

I see that your tools are available for vscode, atom, eclipse and intelliJ, for me NetBeans is missing. Can you please add support for NetBeans as well? That would be great.

Regards

Chris

It works for application.properties file, but there is no tip window when i edit application.yml .
Visual Studio Code version is 1.23.0
vscode-spring-boot version is 0.20-RC.1

In M10, the below line from a properties file is valid ...

my.property=c:\\path\\to\\file

In M12 it is not, and you get warnings such as ...

- missing LineBreak at 't' - missing LineBreak at '\' - missing LineBreak at 'f' - missing LineBreak at '\' - missing LineBreak at 'p' - missing LineBreak at '\'

Not a huge issue, but thought it should be raised as it is a regression. I suspect it has something do with the below from the M12 changelog ...

"(Eclipse) default editors for Boot properties (application.properties and application.yml files) now based on the generic editor and the language server support - the old editors are still around, but will be removed in future versions of STS4"