Read the debug messages: Make sure the Devtools are undocked into a separate window (open the three-dot Chrome Devtools settings menu and select the first icon from "Dock side"). It never hurts to turn things off and on again.
If the links don't open in your IDE, try one or more of the following steps: For example, if your site is (live) and yoursite.priv (local)) and within your IntelliJ project the web root for this site is under dist/web/, enter those site names under Site and the path under Root Path. Under Root Paths set up the path mappings for your project. Method 2: In Chrome go to chrome://extensions/ -> Open In Intellij -> Options.Method 1: In IntelliJ right-click on the the directory that is the web root of the project and select Mark directory as -> Sources Root.If the web root of your IntelliJ project is different from your project root, you have to do one the following methods in order for this extension to work: Now the resource will be opened in your IDE. Open the corresponding website in Chrome, inspect it, right-click on any resource and select Open in IntelliJ. Open one of your projects in your IntelliJ IDE (WebStorm, PHPStorm etc.). Under Extensions -> Link Handling select Open In IntelliJ. If you want to open all files in IntelliJ automatically, open Chrome DevTools, go to Settings. Now you can right-click on any file link in Chrome Devtools and select "Open using Open In IntelliJ".
#WEBSTORM 404 NOT FOUND INSTALL#
Install the extension from the Chrome Web Store: This is an extension for Google Chrome to open resources from the Dev Tools (like CSS, SCSS, JS files) directly inside your JetBrains IntelliJ IDE (IntelliJ IDEA, WebStorm, PHPStorm etc.) > Process 'command '/home/gradle/.gradle/caches/modules-2/files-2.1/com.jetbrains/jbre/jbrx-8u202-linux-圆4-b1483.31/jre/bin/java'' finished with non-zero exit value 8Ĭom.: While loading class : org/./ij/MyPluginStarter has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 Īt .cl.PluginClassLoader.loadClassInsideSelf(PluginClassLoader.java:185) at .cl.yLoadingClass(PluginClassLoader.java:136) at .cl.PluginClassLoader.loadClass(PluginClassLoader.java:49) at (ClassLoader.java:357) at 0(Native Method) at (Class.java:348) at .(ComponentManagerImpl.java:367) at .(ComponentManagerImpl.java:81) at .(ApplicationImpl.java:407) at .(ApplicationImpl.java:393) at .run(IdeaApplication.java:208) at .lambda$initApplication$0(IdeaApplication.java:74) at .dispatch(InvocationEvent.java:311) at (EventQueue.java:764) at $500(EventQueue.java:98) at $3.run(EventQueue.java:715) at $3.run(EventQueue.java:709) at (Native Method) at $JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74) at (EventQueue.java:734) at .dispatchEvent(IdeEventQueue.java:346) at (EventDispatchThread.java:205) at (EventDispatchThread.java:116) at (EventDispatchThread.java:105) at (EventDispatchThread.java:101) at (EventDispatchThread.java:93) at (EventDispatchThread.Open in IntelliJ - Chrome DevTools Extension Execution failed for task ':buildSearchableOptions'.
FAILURE: Build failed with an exception. :buildSearchableOptions (Thread) completed.
#WEBSTORM 404 NOT FOUND DOWNLOAD#
Yes, it can be skipped by -x buildSearchableOptions but is there an option to tell this task to download Java 11 jbre rather. Because 'buildSearchableOptions' downloads jbrx-8u202 everytime. What is the task 'buildSearchableOptions' for? This makes the 'build' task fail for Java 11 compiled plugins.