Fork me on GitHub
#cursive
<
2016-08-18
>
onetom04:08:31

I was seeing this message after the latest IntelliJ & Cursive updates > Your project requires namespaces which need stubs to be generated BUT 1. it was not clear it was coming from Cursive and not IntelliJ 2. I was trying to google the message but nothing found 3. Finally I found the https://cursive-ide.com/archive/2129.html email here slack when i searched for stubs I think it would be good to mention the full message somewhere (on the mailing list for example), so it's easier to track down what is it about

cfleming04:08:10

@onetom: It does mention namespaces which suggests Cursive, but yes, fair point.

cfleming04:08:37

That message has been confusing for people who didn’t see the release announcement, I’m not sure what the best place to put info about it is.

cfleming04:08:39

I’ll be adding this to the documentation once the feature is stable, at that point it should be easier to Google.

onetom04:08:18

indeed, the mention of namespaces gives it away... thanks for the feedback. actually the message will appear on https://clojurians-log.clojureverse.org/cursive/2016-08-18.html soon; that should be enough

onetom04:08:14

amazing work, btw thanks for all these efforts in the name of the team

cfleming04:08:52

No problem, hopefully this will be helpful!

cfleming04:08:08

It’ll hopefully allow good support of libraries that are very difficult right now.

onetom04:08:58

that datomic stub jar you made earlier was actually a satisfactory solution.

onetom04:08:43

setting javelin defc, defc= and hoplon defelem to be treated as defs are also good enough

onetom04:08:01

where are these settings stored, btw?

onetom04:08:11

is it possible to version control it with our projects?

cfleming04:08:20

Yes, although various people mentioned that the jar solution was annoying when using cloud hosted CI solutions.

cfleming04:08:56

Actually, hoplon is one that this support might help for as well, I haven’t looked at it yet though.

cfleming04:08:44

Currently they’re stored IDE-wide, because I figured that you would not want to have to set them up per-project every time you create a new project.

cfleming04:08:03

Those settings can be shared between users by using the settings repository plugin, although I haven’t tried it.

cfleming04:08:24

I’ll try to test that out soon, since it’s a very reasonable thing to want to do.

onetom04:08:07

the settings repo plugin needs a jetbrains account though, right?

onetom04:08:15

ah, you were referring to this plugin, right: https://github.com/develar/settings-repository

cfleming05:08:00

@onetom: Right, that’s the one, it’s built in.

cfleming05:08:33

So it’s documented in the official IntelliJ docs