Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't warn if Clojure or ClojureScript are out of date dependencies #28

Open
danielcompton opened this issue May 12, 2016 · 0 comments
Open

Don't warn if Clojure or ClojureScript are out of date dependencies #28

danielcompton opened this issue May 12, 2016 · 0 comments

Comments

@danielcompton
Copy link

Clojure and ClojureScript are special dependencies, in that the user is always going to be providing their own version which will override the ones in the project.clj. It is good for projects to maintain backwards compatibility with older versions of Clojure, so they shouldn't be penalised for it, in whatever small way a badge showing outdated dependencies counts as a penalty :)
danielcompton added a commit to danielcompton/jarkeeper.com that referenced this issue May 12, 2016
@danielcompton
Remove Clojure dependencies from being counted as outdated
5b7c85f 
Remove Clojure dependencies before counting stats on whether they are up
to date or not.

There are lots of reasons why a project doesn't have the latest Clojure
version, and there is nothing particularly wrong with that dep being out
of date, as a user's own Clojure will take precedence over the one in
the dep.

- Update Clojure to 1.8
- Add sift function to simplify the stats calculation code

Fixes hashobject#28
@danielcompton danielcompton mentioned this issue May 12, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danielcompton