"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

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

even if they're in the dev profile?

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

oh wait I think I know what's causing it

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

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

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

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

unless maven scopes can be set without using profiles?

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

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

the plugin doesn't have its own profile

is probably part of the problem

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

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