1. 04 Nov, 2016 1 commit
  2. 11 Oct, 2016 1 commit
    • Chris Price's avatar
      (#2216) Fix bug with managed deps in profiles w/:replace · 6c69f563
      Chris Price authored
      Prior to this commit, profiles with `^:replace` on the dependencies
      list would never end up having their dependencies vector normalized
      so that it would have `nil` placeholders for the versions of
      dependencies that were inheriting their version from `:managed-dependencies`.
      
      This commit normalizes the dependencies vector of a profile during
      initialization, to make sure that it will always be normalized.
      6c69f563
  3. 18 Sep, 2016 1 commit
    • Chris Price's avatar
      Don't require `nil` for version in managed deps - fixes #2195 · 5bd091a2
      Chris Price authored
      Prior to this commit, if you wanted to use modifiers such as
      `:exclusions` or `:classifier` for a dependency whose version you
      were managing with `:managed-dependencies`, you would need to
      explicitly pass a `nil` as the version string in the dependency
      tuple.  This commit adds some logic to coerce the vectors before
      they are processed, so that if the version string is simply
      omitted instead of being set to `nil`, the `nil` will be implicitly
      inserted and things will continue to work as before.
      
      This provides a slightly nicer and more intuitive UX for the
      managed-dependencies feature.
      5bd091a2
  4. 16 Sep, 2016 1 commit
    • Chris Price's avatar
      Fix checking for SNAPSHOT deps with managed deps - fixes #2205 · 3feae04e
      Chris Price authored
      This commit fixes #2205: when using managed dependencies in
      a project, if the project itself was a non-SNAPSHOT version,
      then when `lein install` and similar tasks were executed,
      lein would check to make sure that none of the dependencies
      were a SNAPSHOT version.  lein was checking that directly against
      the `:dependencies` vector, which would cause an NPE if a dependency
      didn't specify a version number (because it was inheriting it from
      the `:managed-dependencies` section).
      
      This commit fixes the bug by calling the code that merges the
      `:dependencies` and `:managed-dependencies` vectors together prior
      to performing the SNAPSHOT check.
      3feae04e
  5. 30 Jun, 2016 1 commit
    • Chris Price's avatar
      Clarify docs, add tests for transitive deps · 7ea847d1
      Chris Price authored
      This commit clarifies some things in the docs based on PR review.
      It also adds additional test coverage for managed dependencies;
      specifically, a case where two normal dependencies both have
      a transitive dependency on the same library, but with different
      versions.  The test validates that this conflict is properly
      resolved via `:managed-dependencies`.
      7ea847d1
  6. 22 Jun, 2016 2 commits
    • Chris Price's avatar
      (#2067) Improve test coverage for managed dependencies · 54fda200
      Chris Price authored
      This commit adds some additional dependencies to the test project
      file for managed dependencies, and significantly increases the
      coverage of the tests.
      54fda200
    • Chris Price's avatar
      (#2067) add support for `managed-dependencies` · 27782edb
      Chris Price authored
      This commit provides initial support for `managed-dependencies`,
      where dependency version numbers may be specified in a separate
      section called `managed-dependencies`, and those version numbers
      will be used for any deps in the main `dependencies` section
      that do not explicitly specify a version number.
      
      This is a precursor to being able to specify a "parent" project
      that could be used to consolidate version numbers of common
      dependencies across a large number of libraries.
      27782edb
  7. 29 Apr, 2016 1 commit
  8. 04 Feb, 2016 1 commit
    • Jean Niklas L'orange's avatar
      Print meta when eval-in-subprocess · 99d53683
      Jean Niklas L'orange authored
      This fixes the issue with reflection warnings in #2045, but
      unfortunately breaks backwards compatibility with 1.1.0. So the lowest
      version of Clojure Leiningen now supports is 1.2.0.
      99d53683
  9. 21 Jan, 2016 1 commit
  10. 23 Jul, 2015 1 commit
  11. 18 Jul, 2015 1 commit
  12. 16 Jul, 2015 1 commit
  13. 25 Oct, 2014 1 commit
  14. 22 Oct, 2014 1 commit
  15. 23 Sep, 2014 1 commit
  16. 16 Sep, 2014 1 commit
  17. 09 Sep, 2014 2 commits
    • Phil Hagelberg's avatar
      9a044804
    • Hugo Duncan's avatar
      Add profile metadata · 2da05e63
      Hugo Duncan authored
      Adds :leaky and :pom-scope metadata for profiles.  The :dev, :test,
      :base and :provided profiles are implemented in terms of these.
      
      Profiles with :leaky metadata affect the pom and jar creation.
      
      Profiles with a :pom-scope metadata of :test or :provided also affect
      the dependencies of a pom.
      2da05e63
  18. 08 Sep, 2014 1 commit
    • Phil Hagelberg's avatar
      Revert addition of :downstream profile. · c8806ff1
      Phil Hagelberg authored
      We need to revisit this in a way that doesn't involve hard-coding
      profile names into the jar and pom tasks. The question of whether the
      profile should be visible to downstream consumers should be determined
      by data that's part of the profile (or metadata).
      c8806ff1
  19. 06 Sep, 2014 1 commit
  20. 01 Sep, 2014 1 commit
  21. 22 Apr, 2014 1 commit
  22. 26 Mar, 2014 1 commit
  23. 17 Mar, 2014 1 commit
  24. 14 Mar, 2014 2 commits
    • Gary Fredericks's avatar
      b19b305d
    • Gary Fredericks's avatar
      lein run: don't catch app errors as require errors · cc886d56
      Gary Fredericks authored
      closes #1469
      
      `lein run` currently has some special error handling around
      FileNotFoundException which helps it decide what exactly it should
      do. Unfortunately if the actual running of the given main function
      itself throws a FileNotFoundException this is currently caught by
      Leiningen and assumed to be a require error.
      
      The simple solution is to run the main method outside of that error
      handling block.
      
      Regression test provided.
      cc886d56
  25. 17 Dec, 2013 1 commit
  26. 14 Oct, 2013 1 commit
  27. 05 Oct, 2013 1 commit
  28. 01 Oct, 2013 1 commit
  29. 29 Aug, 2013 1 commit
  30. 24 Aug, 2013 1 commit
  31. 21 Aug, 2013 1 commit
  32. 01 Aug, 2013 1 commit
    • Gary Fredericks's avatar
      #1269: Skip tests differently when using :test-selectors · 08eaf707
      Gary Fredericks authored
      The old method skipped tests by adding a hook to
      clojure.test/test-var, the problem being that :each fixtures
      associated with the test have already run at that point, which is
      unideal.
      
      This change skips test by removing their :test metadata before running
      the tests at all, which causes clojure.test to not see it as a test.
      
      We use ns-interns to enumerate the vars, the same way clojure.test
      does.
      08eaf707
  33. 25 Jul, 2013 1 commit
  34. 06 Jul, 2013 1 commit
  35. 22 May, 2013 1 commit
    • Gary Fredericks's avatar
      Don't try static methods on `lein run`: better error msg · 71e609c8
      Gary Fredericks authored
      lein run tries to support invoking static methods on classes by
      swallowing FileNotFoundExceptions when requiring the namespace to run,
      which can obscure the real error when there's a real issue loading a
      namespace.
      
      Phil said he wasn't interested in keeping the (undocumented) feature
      around, so the easiest fix to the error message problem was to remove
      that feature.
      
      Added a test as well.
      71e609c8
  36. 19 Mar, 2013 1 commit
  37. 17 Nov, 2012 1 commit