![]() to be set (see the specific configuration options for Maven, Gradle, Ant, CLI, and Jenkins). This is not systematic BTW, it sometimes works fine (and my dependencies are in the classpath) but eventually stops working. Out of the box dependency-check uses a local H2 database. Once IntelliJ IDEA has reloaded our updated build file with the new dependency, this new dependency will appear in our external libraries in the project window. This would be fine if it stayed that way, but every single time I "Refresh All Gradle Projects" (because I add a dependency or whatever) they go back to "Provided" and I run into the error once again. Selecting one of the suggestions in the message Pressing on the Refresh Gradle icon in the top right, Using the keyboard shortcut I (macOS), or Ctrl+Shift+O (Windows/Linux). Going back to the Project Structure window and marking the dependencies as "Compile" one by one and then running again was the only way to get them to be included in the `-classpath` argument (thus getting rid of the ClassNotFoundException). However, running / debugging directly from IntelliJ, I get a ClassNotFoundException on one of my dependencies : Caused by: : io.grpc.BindableServiceĪt (URLClassLoader.java:381)Īt (ClassLoader.java:424)Īt $AppClassLoader.loadClass(Launcher.java:331)Īt (ClassLoader.java:357)ĭigging a bit deeper, I realized that my dependencies were missing from the -classpath argument altogether ! Looking at my project structure, all the dependencies are "Provided" : I'm using IntelliJ IDEA 2016.3.1 with the Gradle integration.įrom the Gradle window, when I click Refresh All Gradle Projects, I see the external dependencies just fine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |