IntelliJ does not create the files in src_managed

[kwalcock]

Several of our projects have automatically generated source code. One kind is from the sbt-buildinfo plugin, which allows us to record build information in source code and have it compiled into the jar. Another kind is one specific to Eidos, the Versioner, which is used to add version information to the ontologies that are automatically retrieved from github. This is because Ben needs to know that everyone used the same ontology, or at least know what different one was used.

For most of the projects, that's the end of it. IntelliJ is not interested in these files and sbt will build as expected. Eidos, however, makes more active use of these files and IntelliJ needs to know about them. Unfortunately, with the version of sbt we're using, the scala plugin version, the build.sbt file, and anything else influencing the situation, the source files that sbt would normally produce in target/scala-2.12/src_managed are not generated if only IntelliJ is used. Build problems will ensue.

Right now it appears that the way around it is to make sure that sbt builds the project once and produces the files. After that, IntelliJ seems to be able to use them. It may be that this was the behavior the entire time and that anyone using IntelliJ happened to run sbt as well. Just recently that has not been the case.

[kwalcock]

@JerryZeyu, thanks for discovering this problem. @vanh17, you might run into this if you move to Windows and use IntelliJ without sbt.