Report correctly on managed-dependencies

[ikitommi]

When versions are defined via :managed-dependencies, the report doesn't shot the version. eg..

(defproject kikka "0.1.0-SNAPSHOT"
  :managed-dependencies [[metosin/spec-tools "0.4.0"]]
  :dependencies [[metosin/spec-tools]])

with lein ancient it prints:

[metosin/spec-tools "0.5.0"] is available but we use ""

and thanks for the awesome plugin!

[danieltdt]

Any news about it?

[awb99]

yeah!! A fix for this would really help!

[awb99]

Is there anyone stil workinng on lein-ancient?
A fix for managed-dependenies to me is a pretty important feature. I know it is a new leiningen feature, so implementation will take a while. However, the reason to use lein-ancient is for BIG projects, where it is very difficult to manage dependencies. And such projects will use managed-dependencies sooner or later. THANKS!

[xsc]

@awb99 I'm slowly finding time to get back into these projects. Since I have not been actively working on them for a few months, it might still take a bit until I've familiarized myself again.

Give me a bit of time - this doesn't look too hard to fix.

[xsc]

About 3 years too late, but I just pushed [lein-ancient "0.7.0-SNAPSHOT"] which should incorporate a fix for this. Could one of you reading this check it out? Thanks!

[dancek]

@xsc 0.7.0-SNAPSHOT fixed the issue for the parent project that has :managed-dependencies.

In a child project, however, all the dependencies are listed with version "". Child project meaning that the project.clj has

  :plugins [[lein-parent "0.3.8"]]
  :parent-project {:path    "modules/parent/project.clj"
                   :inherit [:managed-dependencies]}

In any case, the current fix is very useful. 👍

[dcarley]

I forgot to report it, but experienced the same 👍

[xsc]

I deployed another SNAPSHOT that might fix the issue with parent projects. (It now uses the project map that Leiningen provides to find managed dependencies, instead of collecting them from the file itself.)

[dancek]

@xsc this new snapshot version shows all artifacts are up-to-date. for a child project even when some of the dependencies are out of date. The parent project has correct version listings.

[xsc]

@dancek Right now, the plugin won't check dependencies of the parent project if run in a child project. Is that what you mean or are there actual outdated dependencies in the child project's project.clj?

[dancek]

@xsc yeah, that's what I meant. I have all the dependency versions in the parent project. I.e. I use the parent project mostly to keep multiple child projects using the same dependency versions.

[dancek]

In any case, I think the current version is good for release.

[xsc]

Current fix released in [lein-ancient "0.7.0"]. Tracking the parent dependency topic in #119, please share your opinion there. :)