Build does nothing
7 人关注
On IntelliJ 2017.3, nothing seems to happen when I build or rebuild my project. The event log says that all files are up to date, but no out or build directory is created. idea.log has these informational messages:
INFO - ij.compiler.impl.CompileDriver - COMPILATION STARTED (BUILD PROCESS)
INFO - j.compiler.server.BuildManager - Using preloaded build process to compile C:\Users\joe\Google Drive\Hibernate class\Lab 2 - HelloWorld\HelloWorld
INFO - lij.compiler.impl.CompilerUtil - COMPILATION FINISHED (BUILD PROCESS); Errors: 0; warnings: 0 took 493 ms: 0 min 0sec
INFO - s.CompilerReferenceServiceImpl - backward reference index reader is opened
INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stdout]: Build process started. Classpath: C:/Program Files/JetBrains/IntelliJ IDEA 2017.3/lib/jps-launcher.jar;C:/Program Files/Java/jdk-9.0.1/lib/tools.jar;C:/Program Files/JetBrains/IntelliJ IDEA 2017.3/lib/optimizedFileManager.jar
INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: An illegal reflective access operation has occurred
INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil (file:/C:/Program%20Files/JetBrains/IntelliJ%20IDEA%202017.3/lib/netty-all-4.1.13.Final.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: Please consider reporting this to the maintainers of io.netty.util.internal.ReflectionUtil
INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: All illegal access operations will be denied in a future release
请先登录再写评论。
To which folder the module's compiler output is configured for project? Check the output in those directories after full project rebuild.
If issue remains, please clarify do you use Gradle/Maven? Attach screenshot of the project tool window with expanded there classes.
Does it work with other project under the same common folder?
Does it help to relocate project to folder outside of Google Drive?
The compiler output path for the project is set to
C:\Users\joe\Google Drive\Hibernate class\Lab 2 - HelloWorld\HelloWorld\out, and the module is set to inherit the project's compile output path.
I do not use Gradle or Maven currently. Here is the project tool window:
No difference in the UI if I move the project outside of Google Drive, but the logs in idea.log are different:
2018-01-15 11:13:33,633 [ 505678] INFO - ij.compiler.impl.CompileDriver - COMPILATION STARTED (BUILD PROCESS)
2018-01-15 11:13:33,635 [ 505680] INFO - j.compiler.server.BuildManager - Using preloaded build process to compile C:\Users\joe\Downloads\HelloWorld
2018-01-15 11:13:34,407 [ 506452] INFO - lij.compiler.impl.CompilerUtil - COMPILATION FINISHED (BUILD PROCESS); Errors: 0; warnings: 0 took 780 ms: 0 min 0sec
2018-01-15 11:13:34,413 [ 506458] INFO - s.CompilerReferenceServiceImpl - backward reference index reader is opened
2018-01-15 11:13:34,929 [ 506974] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stdout]: Build process started. Classpath: C:/Program Files/JetBrains/IntelliJ IDEA 2017.3/lib/jps-launcher.jar;C:/Program Files/Java/jdk-9.0.1/lib/tools.jar;C:/Program Files/JetBrains/IntelliJ IDEA 2017.3/lib/optimizedFileManager.jar
2018-01-15 11:13:34,977 [ 507022] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
2018-01-15 11:13:34,977 [ 507022] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: SLF4J: Defaulting to no-operation (NOP) logger implementation
2018-01-15 11:13:34,977 [ 507022] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
2018-01-15 11:13:35,140 [ 507185] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: An illegal reflective access operation has occurred
2018-01-15 11:13:35,141 [ 507186] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil (file:/C:/Program%20Files/JetBrains/IntelliJ%20IDEA%202017.3/lib/netty-all-4.1.13.Final.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
2018-01-15 11:13:35,141 [ 507186] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: Please consider reporting this to the maintainers of io.netty.util.internal.ReflectionUtil
2018-01-15 11:13:35,141 [ 507186] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
2018-01-15 11:13:35,141 [ 507186] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: WARNING: All illegal access operations will be denied in a future release
I created a new project from sources in the same location, and now building works. Weird.
You need to mark src folder as a source root, see Adding and removing content roots
Yes, I had done that in the original project.
Same problem here. The template java command line project didn't work.
New project from same directory workaround worked too.
Disturbing... :)
Same problem here, same fix. It's kind of confusing to have to tell my class "set up the project like X, Y, Z, but then the IDE that's supposed to compile everything for you doesn't actually like to compile anything, so go through this long process to close everything and re-import the directory that you just created, and jump through some other hoops to add your artifacts back..."
Same issue here. I deleted .idea/ and *.iml, restarted, reimported, reconfigured, however, still doesn't work. I am unable to perform my job right now.
jpittard Please file a bug at https://youtrack.jetbrains.com/newIssue?project=IDEA and attach the logs using Help | Collect Logs and Diagnostic Data.
Just happened to a coworker; deleting the whole project and then redownloading it from our VCS fixed it for him as well. His version of intelliJ is 2023.2.2