I used to rely on the fact that when Cursive is reading project.clj, the current working directory is the folder which contains project.clj. That seems to be no longer the case with IDEA 2016.3 EAP and Cursive 1.4.0-eap3-2016.3.
Also this exposed another minor issue. Cursive does not give meaningful feedback. It just reports that project.clj does not exist and prints a path which obviously exists. I had to try to comment out different parts of the project.clj map to find offending piece and then realized that Cursive has problem reading the file due to an exception in my own inlined code.
It would be helpful to display better error report in cases like that.
Background info:
I'm using ~(slurp "project.clj") in my project.clj to read back some other parts of project.clj to generate another part of project.clj config[1]. Haven't found a better way to do that.
[1] https://github.com/binaryage/dirac/blob/432c03e4b3337ff0d0ad188393848dbb7d55d772/project.clj#L102-L103
I used to rely on the fact that when Cursive is reading project.clj, the current working directory is the folder which contains project.clj. That seems to be no longer the case with IDEA 2016.3 EAP and Cursive 1.4.0-eap3-2016.3.
Also this exposed another minor issue. Cursive does not give meaningful feedback. It just reports that project.clj does not exist and prints a path which obviously exists. I had to try to comment out different parts of the project.clj map to find offending piece and then realized that Cursive has problem reading the file due to an exception in my own inlined code.
It would be helpful to display better error report in cases like that.
Background info:
I'm using
~(slurp "project.clj")in my project.clj to read back some other parts of project.clj to generate another part of project.clj config[1]. Haven't found a better way to do that.[1] https://github.com/binaryage/dirac/blob/432c03e4b3337ff0d0ad188393848dbb7d55d772/project.clj#L102-L103