Open danielcompton opened 7 years ago
For starters it would be enough to not show the warning. The warning tells me nothing I do not already know. I cannot do anything to change the situation. So the warning is just pure pain to me
Just noticed that deps-new generates a build.clj
at the top level of a project
Which suffers from a similar issue
Using (clojure -Tnew app :name myusername/mynewapp)
Ah looks like the issue is that I didn't have the build aliases selected:
even with aliases base functionality doesn't work
@kwladyka Sometimes picking the new deps up can be flakey, which seems to be an IntelliJ problem. If you close and reopen your project, does that fix it?
I have checked right now and it works.
@cursive-ide I have a similar problem in a multi-module Clojure project. If I open one of the modules in an own IntelliJ window, the source code, which lives under project/tasks/src
and is included in :paths
for the module's deps.edn
file, I get this error, which prevents me from using Parinfer to indent code:
Under Project Settings -> Modules, it shows this:
I tried adding the tasks module path "src" via "Add Content Root", but then it complains about this:
Could Cursive please not disable Clojure editing just because it can't figure out what the path means? Thanks!
When using Boot, the
build.boot
is at the same level asproject.clj
in most projects. However it is treated as being outside of a source root, so a warning is shown. It would be handy ifbuild.boot
files were:project.clj
files, where you don't get warned about being outside a source root.