# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Without this, tools such as grenchman will write project.clj to the
directory from which Leiningen was launched.
Also make require-resolve work like resolve for unqualified symbols.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
1. Reorganise tests a bit so loading property still checked.
2. Add explicit exception if unexpected type to `collapse-function`
3. Unrelated addition of test to show leading `:` ignored in nested paths
Failure must have something to do with namespace state that
changes between running tests in REPL and running the full suite.
Test is not an important property, so just commenting out.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Since release-tasks could include any number of lein-change calls, seems like a
good idea to re-read project.clj between tasks.
Signed-off-by: Wayne <wayne@puppetlabs.com>
Not sure what you think of creating this kind of coupling in the tests.
This were useful tests for driving the previous commits, but happy to
delete them now.
