2018.1 breaks artifact builds when "Store generated project files externally" is checked

Answered

This is the weirdest behavior I've ever come across on IntellIJ - it doesn't make sense because "Store generated project files externally" seems to only be about *.iml and other IntelliJ project files.

But after I upgraded to 2018.1, my tomcat project stopped deploying. In the deploy directory (target/projectname-version), I would only see WEB-INF and META-INF, and none of the assets. We deployed by building the exploded war artifact that was auto generated from our pom.xml.

It took three days of rebuilding indexes, re-importing the (large) project, testing different code versions, etc to figure out what the problem was. I finally started comparing IntelliJ settings with others who were successfully deploying with 2018.1.

I had "Store generated project files externally" checked, and they didn't. When I unchecked it, I was able to deploy.

I have no memory of checking this option - if it existed pre 2018.1, it never caused this problem. This deployment problem didn't start happening until I upgraded to 2018.1 .

 

0
4 comments

Hi, sounds like a duplicate of https://youtrack.jetbrains.com/issue/IDEA-189112, please check the EAP, problem should be fixed there.

0
Avatar
Permanently deleted user

I'm currently facing a similar issue. I'm running on Intellij #IU-181.4892.42. My scenario: Java Gradle project with integrationTests. I clone my project from repo, import using gradle, all modules / sources are created correctly but it fails to build the integrationTests classes because this setting is enabled by default. I have to go to Gradle Settings and uncheck the option so that the build works.

As a workaround, is there a way to make this setting disabled by default (and remain disable when importing a project)?

0

Please file a bug at https://youtrack.jetbrains.com/issues/IDEA and attach a sample project to reproduce the issue.

There is also no way to set "Store generated project files externally" option globally or when importing for Gradle projects. It's available for Maven project, but doesn't work, according to https://youtrack.jetbrains.com/issue/IDEA-181119 and is not available when importing for Maven too: https://youtrack.jetbrains.com/issue/IDEA-181110. Another request for making it a global option and an option in the import dialog for Gradle is welcome as well. Thank you.

0

Please sign in to leave a comment.