Adding nested lein projects after the fact is less functional than importing at the beginning

[jeff303]

When working with a Leiningen project containing nested projects, these can be imported recursively from the beginning by following these steps. And in that case, everything works well.

However, if later on, you want to add a new sub Lein project (via the Add Leiningen File button in the Leiningen tool window), the functionality is limited somehow (symbols to other modules don't resolve properly). The problem is that redoing the working full import requires wiping out the project, which is impractical to do on a regular basis. And if sub projects are added or removed in different branches, this becomes unworkable.

It would be great if the Add Leiningen File worked as perfectly as the "recursive import of sub projects" that happens at the initial project creation.

[jeff303]

Figured something out here, maybe. I saw a warning that metabase-core (the root module, which is the parent of all others) can't be managed by Leiningen since it's already managed by Maven. I don't know how it came to be managed by Maven in the first place (we do have a pom.xml at the root, but I never asked IntelliJ for it to be used). But anyway, I did the following:

1. Unlinked the Maven module for metabase-core
2. Manually added the root level project.clj back using the Lein plugin (+ button)
3. Did a lein refresh of all projects

When this finished, and I generated stubs for metabase-core (which the plugin prompted me to), then the symbol resolution started working properly.

[jeff303]

In any case, it would be very useful if the modules could be "remembered" when switching branches. Ex: if master contains a nested module called new-thing, and I switch to old-branch, it goes away. But if I checkout master again, I have to manually add new-thing again as a fresh Lein module. The Maven plugin, at least, seems to handle this (when working with Java projects): I guess it remembers the module from the last time it was present.