How do I downgrade the compiler to a lower java version, like 8?

This happens when I use the "Run" functionality in the main

Using the Java Extension Pack

Whenever I type something, automatically VS Code scrolls up a bit.

I tried to clarify whether this was really because of vscode-java-pack, and I found out, whenever I remove Java Pack extension, everything works fine.

Here's video link (Unlisted) which showcases, VS Code automatically scrolling up whenever I hit space.
https://youtu.be/n7ziWJbog2Q

I installed the Java pack. When i try to open a Java file, I have an error popup saying that a command is missing.
In Log (Window) there are several stacktraces (including one with the message mentioned):

[2018-10-08 10:44:19.209] [renderer1] [info] no standard startup: panel is active
[2018-10-08 10:44:27.930] [renderer1] [error] command 'java.open.output' already exists: Error: command 'java.open.output' already exists
	at e.registerCommand (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:725:618)
	at Object.registerCommand (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:799:950)
	at languageClient.onReady.then (C:\Users\Aurelien Pupier\.vscode\extensions\redhat.java-0.32.0\out\src\extension.js:187:39)
	at propagateAslWrapper (C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\index.js:502:23)
	at C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\glue.js:188:31
	at C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\index.js:539:70
	at C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\glue.js:188:31
	at <anonymous>
[2018-10-08 10:50:42.773] [renderer1] [info] no standard startup: not just one text editor
[2018-10-08 10:50:49.911] [renderer1] [error] command 'java.open.output' already exists: Error: command 'java.open.output' already exists
	at e.registerCommand (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:725:618)
	at Object.registerCommand (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:799:950)
	at languageClient.onReady.then (C:\Users\Aurelien Pupier\.vscode\extensions\redhat.java-0.32.0\out\src\extension.js:187:39)
	at propagateAslWrapper (C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\index.js:502:23)
	at C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\glue.js:188:31
	at C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\index.js:539:70
	at C:\Users\Aurelien Pupier\.vscode\extensions\vscjava.vscode-java-pack-0.4.0\node_modules\async-listener\glue.js:188:31
	at <anonymous>
[2018-10-08 10:57:37.949] [renderer1] [error] command 'java.execute.workspaceCommand' not found: Error: command 'java.execute.workspaceCommand' not found
    at t._tryExecuteCommand (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3019:717)
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3019:572
    at n.Class.derive._oncancel.then (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:161:366)
    at t.executeCommand (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3019:546)
    at e.$executeCommand (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3174:846)
    at e._doInvokeHandler (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3235:593)
    at e._invokeHandler (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3235:311)
    at e._receiveRequest (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3234:129)
    at e._receiveOneMessage (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3233:270)
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3232:74
    at e.fire (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:175:76)
    at a (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:311:740)
    at Socket.n._socketDataListener (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:311:959)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)
[2018-10-08 10:57:39.351] [renderer1] [error] command 'java.execute.workspaceCommand' not found: Error: command 'java.execute.workspaceCommand' not found
    at t._tryExecuteCommand (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3019:717)
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3019:572
    at n.Class.derive._oncancel.then (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:161:366)
    at t.executeCommand (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3019:546)
    at e.$executeCommand (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3174:846)
    at e._doInvokeHandler (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3235:593)
    at e._invokeHandler (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3235:311)
    at e._receiveRequest (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3234:129)
    at e._receiveOneMessage (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3233:270)
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3232:74
    at e.fire (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:175:76)
    at a (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:311:740)
    at Socket.n._socketDataListener (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:311:959)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)

• Issue Type: Performance
• Extension Name: vscode-java-pack
• Extension Version: 0.5.0
• OS Version: Darwin x64 17.7.0
• VSCode version: 1.30.0
  vscjava.vscode-java-pack-unresponsive.cpuprofile.txt

VS Code recognizes that OpenJDK is not downloaded and informs user to download it from
https://developers.redhat.com/products/openjdk/overview/

Upon doing so, the user is still unable to use javac to compile the code. They receive the error
"'javac' is not recognized as an internal or external command, operable program or batch file."

This is very frustrating to new users, and those who are rusty towards knowing about pathing and environment variables. At this point, the user is still stuck despite following VS Code prompt.

Once the JDK is downloaded, VS Code should probably either auto include the path in its built in terminal, or prompt the user to locate the JDK to add the path. At the very least, it could send a reminder that the pathing needs to be updated in order to use it and direct them to a useful link.

This would make setting up VS Code dramatically quicker for those who are just learning coding in general. It would also add convenience for those who are already more adept at coding by giving them one less thing to worry about.

• Use extensionPack to replace extensionDependencies #29 @sandy081 #30
• 🏃Show Java Welcome page #32 @akaroml PR: #35 #36
• Update Readme.md

Legend of annotations:

thinks~~

Unable to use side-scrolling on the mouse within Visual studio code. It jumps to where the cursor is on screen, but cannot be manually shifted with a scroll wheel that supports side-scrolling

Hello, I am building a mevan java web application but I can not figure out how to export my project to a war file which is I really need. So is it possible ??
kind regards.

Is conceptually correct that "Extension Pack" is actually has own contribution to the VSCode?

• Issue Type: Performance
• Extension Name: vscode-java-pack
• Extension Version: 0.5.0
• OS Version: Darwin x64 18.2.0
• VSCode version: 1.30.2

⚠️ Make sure to attach this file from your home-directory: /Users/sombriks/vscjava.vscode-java-pack-unresponsive.cpuprofile.txt ⚠️

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Hello, how can i execute my JUnit tests in VSCode ? My app run with Java 6 and i can't upgrade it.
Thx.

Issue Type: Bug

The Language Support for Java server crashed 5 times in the last 3 minutes. The server will not be restarted.

Extension version: 0.5.0
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17134

We have lots of Chinese developers. It would be great if we can provide a localized interface. This issue is to track the effort of building the localization story.
Supporting Chinese is a start. Once the solution is working, we can expand the support to other languages.

Here are the issues created to track the progress of related extensions:

• Java Language Server redhat-developer/vscode-java#716
• Java Debugger microsoft/vscode-java-debug#477 PR microsoft/vscode-java-debug#484
• Maven microsoft/vscode-maven#46 PR microsoft/vscode-maven#147
• Java Test Runner microsoft/vscode-java-test#437
• Java Dependency Viewer microsoft/vscode-java-dependency#100

• Issue Type: Performance
• Extension Name: vscode-java-pack
• Extension Version: 0.5.0
• OS Version: Linux x64 4.15.0-39-generic
• VSCode version: 1.30.0

⚠️ Make sure to attach this file from your home-directory: /home/todhelder/vscjava.vscode-java-pack-unresponsive.cpuprofile.txt ⚠️

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

VS Code shows a welcome page on startup. The page provides quick start experience.
For Java users, the similar concept can also apply. VS Code is very different from classical Java IDEs like Eclipse and IntelliJ. New users get lost very easily when trying to adopt this new solution. So a welcome page can solve that problem by providing:

• A list of most used task entries
• Links to the documentation
• Links to sample projects and tutorials

• Issue Type: Performance
• Extension Name: vscode-java-pack
• Extension Version: 0.5.0
• OS Version: Darwin x64 16.7.0
• VSCode version: 1.30.1

⚠️ Make sure to attach this file from your home-directory: /Users/Ken/vscjava.vscode-java-pack-unresponsive.cpuprofile.txt ⚠️

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

From @YousefSaber on November 17, 2017 19:16

how can I debug java source code in the new version of VS Code ??

Copied from original issue: microsoft/vscode#38648

I have tried various techniques to specify the JavaDoc .jar that should be attached to a given library .jar (that appears in the "Referenced Libraries" section of the "JAVA DEPENDENCIES" view, and is successfully used by my app), but nothing has worked.

Currently, the only JavaDoc documentation that appears in the editor for me is that for the built-in objects/members, like Object and toString(). No third-party libraries seem to have any JavaDoc exposed in the editor.

Is there any example of a simple project configured with a dependency on a library .jar (that has an associated JavaDoc .jar, also located on the local file system) where the editor is able to display the documentation comments for selected Java types and members?

If I have multiple vscode windows open with different java projects only one has java language support. If i close the one supported then the other gains support.

Issue Type: Bug

When I tried to use Math class, Double class, etc. The Intellisense is not showing any methods or members about these classes.

Extension version: 0.3.0
VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z)
OS version: Windows_NT x64 10.0.17134

Install

• Be able to install the extension using .vsix package

Present "Java Overview" page

• Present "Java Overview" page automatically when
  • A .java file is opened
  • A Java project is opened
• Should NOT present "Java Overview" automatically when
  • The option "Show overview page when using Java" is unchecked
  • Non-java files/projects are opened
• Show overview page using command "Java: Overview"
• Show overview page by clicking the icon on status bar
  

Links in Overview page

• "Create a Maven project..." should lead users to either of the following
  • Create a Maven project
    
  • Recommend Maven extension when it's not installed
    
• "Create a Spring Boot project..." should lead users to either of the following
  • Create a Spring Boot project
  • Recommend Spring Boot extension when it's not installed
• All documentation links should take users to the web page
• Should NOT recommend an extension when it's already installed, examples:
  • When Maven is installed, you should not see it in the extension recommendation list
    
  • When Maven is not installed, you should see it in the list:
    

Release Notes

• Release Notes should be presented automatically for only once when using Java
• Same version of Release Notes should NOT be presented again after restarting VS Code
  • You can see the version here
    
• Run "Java: Show Release Notes" should show the release notes

In-app recommendation

• XML extension should be recommended when opening POM.XML
• XML extension should not be recommended again when opening POM.XML

In the latest version of vscode, only for Java projects, it get's stuck at "Activating Extensions".

VS Code: Version 1.30.2 (1.30.2)
Java pack: 0.5.0

vim for vscode doesn't work due to this. If I open a non-java project or if I uninstall this extension everything works fine.

Do let me know if you need more info.

Code just refuses to identify jdk 8. But if I right click maven project > myproject and click install, the maven project installs fine.

I keep seeing 1.8 error in problems tab:
"Lambda expressions are allowed only at source level 1.8 or above [1610613381] (line, column)"

User settings.json
"java.home": "/Library/Java/JavaVirtualMachines/jdk1.8.0_191.jdk/Contents/Home",

Code : Version 1.29.1 (1.29.1)
Java Extension Pack 0.4.0
Mac OS High Sierra : Version 10.13.6

Already tried:

• Cleaning up the workspace,
• reinstalling java extension pack,
• restart/reload code.
• importing the same project in eclipse and building with 1.8 works fine.

This extension uses version 0.3.0 of vscode-extension-telemetry-wrapper module.

The latest version of vscode-extension-telemetry-wrapper module (0.3.2) uses the latest version of vscode-extension-telemetry module (0.0.22) which has the fix to prevent unnecessary patching of the require and other 3rd party modules.

For more details, please see Eskibear/vscode-extension-telemetry-wrapper#20

do check the video link

https://drive.google.com/file/d/16bxoqj-4pA_aJAOChTpLpinpaiZCwwQf/view

• Issue Type: Performance
• Extension Name: vscode-java-pack
• Extension Version: 0.5.0
• OS Version: Windows_NT x64 10.0.15063
• VSCode version: 1.30.2

vscjava.vscode-java-pack-unresponsive.cpuprofile.txt

Hi,

I'm not sure if i'm doing it wrong but i wanted to configure the java debug to execute on the open java file without having to specify the exact mainClass name.

Ex:

launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "java",
            "name": "Debug (Launch)",
            "request": "launch",
            "mainClass": "${fileBasename} ",
             "args": ""
        }
}

However, it doesn't recognize "${fileBasename} ". I get the following error:

Failed to resolve classpath: Main class '${fileBasename}' doesn't exist in the workspace.

It would be nice if it actually printed what the '${fileBasename}' was as well.

Thanks,
Derek

This might be an issue with the language server, but I received the same error twice (the number at the end is the same for both) but the message is slightly different. Is the top one a bug?

Why am I getting this error when I try to install

Failed to install 'vscjava.vscode-java-pack'.

This is my environment
Windows 10 Home x64
JDK 8
Latest Visual Studio Code

Every other extension installs but only Java extensions repeatedly fail.
What could be wrong?

VSCode Version: 1.29.1
OS Version: Win and Mac
Steps to Reproduce:

This is a very basic demo about Spring Data for LDAP in unit testing. Please refer to the following code:
@RunWith(SpringRunner.class)
@DataLdapTest
public class DirectoryTests {

@Autowired
private LdapTemplate ldapTemplate;

@test
public void whenFindByTitleThenReturnDiscipline() {
LdapQuery query = LdapQueryBuilder.query().where("objectclass").is("person");

List<String> list = ldapTemplate.search(query, new AttributesMapper<String>() {
    public String mapFromAttributes(Attributes attrs)
            throws NamingException {
        return (String) attrs.get("cn").get();
    }
});

assertThat(list.size()).isEqualTo(3);

}
}

The same code runs well with IntelliJ, but got the following error message with VS Code:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:460)
at org.springframework.ldap.core.support.SimpleDirContextAuthenticationStrategy.setupEnvironment(SimpleDirContextAuthenticationStrategy.java:42)
at org.springframework.ldap.core.support.AbstractContextSource.setupAuthenticatedEnvironment(AbstractContextSource.java:194)
at org.springframework.ldap.core.support.AbstractContextSource.getAuthenticatedEnv(AbstractContextSource.java:582)
at org.springframework.ldap.core.support.AbstractContextSource.doGetContext(AbstractContextSource.java:134)
at org.springframework.ldap.core.support.AbstractContextSource.getReadOnlyContext(AbstractContextSource.java:158)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:357)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:309)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:616)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:586)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:1651)
at cn.focusmedia.workforce.directory.DirectoryTests.whenFindByTitleThenReturnDiscipline(DirectoryTests.java:33)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
at org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:190)
at com.microsoft.java.test.runner.junit4.JUnit4TestReference.run(JUnit4TestReference.java:50)
at com.microsoft.java.test.runner.junit4.CustomizedJUnit4CoreRunner.run(CustomizedJUnit4CoreRunner.java:45)
at com.microsoft.java.test.runner.junit4.JUnit4Launcher.execute(JUnit4Launcher.java:30)
at com.microsoft.java.test.runner.Launcher.main(Launcher.java:53)

Does this issue occur when all extensions are disabled?: Yes/No

With all extensions disabled, Java won't work, will it?

Moved from microsoft/vscode#41971

• VSCode Version: Latest Insiders
• OS Version: Mac OS

Steps to Reproduce:

1. Insert cursor before the first argument (that accesses some property) to the method.
2. Start typing new argument that also accesses property.
3. On suggestion appearance, press Tab to enter suggestion value
   It replaces the old first argument instance with the property from the new argument.

Sample code:

public class Test {
    public int testInt;

    public boolean method(int x, int y, int z) {
        return true;
    }
}

public class Main {
    public static void main(String[] args) {
        Test t = new Test();
        t.method(t.testInt, t.testInt);
    }
}

We need a welcome page that shows on startup to help Java developers to get started:

• Scaffold projects:
  • Spring Boot Initializer
  • Azure Functions
  • Maven Archetypes
• Tutorials
  • How to build, test and debug Java Applications?
  • ...
• Samples
  • Spring Boot PetClinic
  • Todo app on Azure
  • Java Steel Thread
• Documentation
  • code.vs.com/java
  • docs.ms.com/java

Vs Code pops up the error when viewing java files. It links user to a site stating what the warning means and how to disable it.

Nowhere does it actually specify how to properly fix the issue. Anyone new to Java development, especially those just starting out will not know how to fix it. Rather than only telling them what the warning means and how to disable it, it should link them to a site that shows how to properly fix the issue, in addition to what it currently tells them.

My workplace and many others I know use gradle for builds, so having gradle support should be considered for this pack. I use https://github.com/naco-siren/vscode-gradle-language for my gradle work, and it is usually well-maintained.

Java Exception log at debugging console not the font color ，and can not click the Exception to source file;

Hey!

I'd like to propose adding the Java Decompiler extension to this pack.

I've been using the pack on a few projects at my day job. Due to our custom build system our dependencies are mostly prepackaged in Jars. The go to definition command makes a reasonable effort to decompile our dependencies out of the box but it isn't able to bring up the implementation details.

The Java decompiler extension works out of the box with the Red Hat extension and is able to decompile the classes and provide implementation details. 👍

Test Explorer UI is a handy way to explore, run and visualize your tests directly from the test explorer.

I'm wishing for a Test Adapter for Junit et al. I'm really missing a red/green bar...

• Issue Type: Performance
• Extension Name: vscode-java-pack
• Extension Version: 0.5.0
• OS Version: Darwin x64 16.7.0
• VSCode version: 1.30.1

⚠️ Make sure to attach this file from your home-directory: /Users/Ken/vscjava.vscode-java-pack-unresponsive.cpuprofile.txt ⚠️

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

The following files are randomly created in the root of my Gradle project dir:

• bin/*
• .settings
• .classpath
• .project

The three latter I think are specific for the Eclipse IDE or a derivative thereof.

Don't get me started why I think this behavior is totally unprofessional and unacceptable lol.

Showing overview page every time a Java project is opened could block users' workflow. Here to track the effort of only showing the page in the foreground the first time. And later, the page should be shown in the background when the page is not requested by users.

I'm trying to create a new package in my java project in VS Code. I have the extension installed as I get proper java editing in existing files, but when I add a new folder to the src tree or test tree and create a java file, I get a compiler error on the "package" statement telling me that "" is expected as the package and to remove the whole "package com.xxxxxxx;" line.

What am I missing?

Thank you,
Chuck

It would be great if the ability to override values for properties was made available when running/debugging Spring Boot applications.

This would allow a file like application.properties - which might contain variables instead of real values for use with something like Octopus Deploy - to be left as they are, but values for running locally to be specified in the debug config, in a similar manner to the "override properties" feature for Spring Boot apps in Spring Tool Suite:

The extension does not support addition external jar file to the classpath. The only way is to manually add it to .classpath file. Please refer to https://stackoverflow.com/questions/50232557/visual-studio-code-java-extension-howto-add-jar-to-classpath/54535301#54535301

Issue Type: Bug

java.util.concurrent.CompletionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Request workspace/executeClientCommand failed with message: command 'java.classpath.refresh' not found
at java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:375)
at java.util.concurrent.CompletableFuture.join(CompletableFuture.java:1934)
at org.eclipse.jdt.ls.core.internal.JavaClientConnection.executeClientCommand(JavaClientConnection.java:81)
at com.microsoft.java.test.plugin.internal.JavaModelEventProvider.elementChanged(JavaModelEventProvider.java:55)
at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1723)
at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1574)
at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1533)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:774)
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:799)
at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1319)
at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1278)
at org.eclipse.jdt.ls.core.internal.handlers.DocumentLifeCycleHandler.performValidation(DocumentLifeCycleHandler.java:134)
at org.eclipse.jdt.ls.core.internal.handlers.DocumentLifeCycleHandler.access$0(DocumentLifeCycleHandler.java:120)
at org.eclipse.jdt.ls.core.internal.handlers.DocumentLifeCycleHandler$1.runInWorkspace(DocumentLifeCycleHandler.java:88)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
Caused by: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Request workspace/executeClientCommand failed with message: command 'java.classpath.refresh' not found
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleResponse(RemoteEndpoint.java:205)
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:189)
at org.eclipse.jdt.ls.core.internal.ParentProcessWatcher.lambda$0(ParentProcessWatcher.java:83)
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:188)
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:90)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95)
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)

Extension version: 0.3.0
VS Code version: Code - Insiders 1.26.0-insider (bd953248ad6a8e2f8896bfb78b3ae40e0fd47426, 2018-07-06T05:17:37.386Z)
OS version: Windows_NT x64 10.0.16299

The extension is using the openurl module to open a URL in the browser. This is the source reference.

The VS Code API supports this with the command vscode.open ([see] (https://code.visualstudio.com/docs/extensionAPI/vscode-api-commands).

Suggest to replace this call with
vscode.commands.executeCommand('vscode.open', uri);.

• Issue Type: Performance
• Extension Name: vscode-java-pack
• Extension Version: 0.6.0
• OS Version: Windows_NT ia32 6.1.7 601
• VSCode version: 1.31.1

vscjava.vscode-java-pack-unresponsive.cpuprofile.txt

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

page https://code.visualstudio.com/docs/languages/java should be updated for v0.3.0