Fork me on GitHub
#leiningen
<
2018-09-07
>
jcr09:09:19

"Could not read the old stale value for leiningen.core.classpath.extract-native-dependencies , rerunning stale task" - what is that and how to get rid of it? I'm getting this message repeated 4-5 times when starting repl in every project

gfredericks18:09:49

is it expected that a lein plugin should include all of its plugins as dependencies in its pom?

gfredericks18:09:00

even if they're in the dev profile?

gfredericks18:09:13

(I wouldn't expect it in either case, but it seems to be true in both)

gfredericks18:09:15

oh wait I think I know what's causing it

mikerod19:09:58

@gfredericks I don’t think you should need them beyond the profile at all

mikerod19:09:11

but sounds like you may have figured out whatever it was that you needed

gfredericks19:09:55

yeah, the problem was I have a dev plugin (different plugin) that does an (update project :dependencies conj [...]) in its middleware function, and I hadn't considered that this effectively makes that dependency a first class dep

gfredericks19:09:08

I don't think there's a clean way for a plugin to add a dev dependency

gfredericks19:09:32

unless maven scopes can be set without using profiles?

gfredericks19:09:13

hmm; I tried (update project :dependencies conj [foo/bar "blah" :scope "test"]), but lein pom in the project using that plugin still has the dependency in the pom

mikerod20:09:52

Hmm. I’d think the plugin would only add the dependency while it’s profile is active

gfredericks20:09:16

the plugin doesn't have its own profile

gfredericks20:09:22

is probably part of the problem

mikerod20:09:25

So that is somewhat surprising to me. Then again, when it comes to like the pom that is generated, things can get a bit confusing with the profiles that are unmerged etc during those times

mikerod20:09:49

if the plugin was isolated to being used from within a profile, I’d think it might work, but really hard to say hah