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.
# 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.
It used to be we would merge a bunch of profiles into the project, and
then trim out dupes based on group/artifact/version, which was totally
wrong; it ignores classifiers and extensions.
I decided to leave some messages alone. Specifically
* messages which look like stacktraces
* messages which instruct the user to take some sort of action
Arguably the stacktraces should go to stderr but I thought I'd leave
those open for discussion. Any others that remain represent errors on
my part.
When running on OS X, an exception thrown in a plugin was resulting in
no output from lein. Adding the flush ensures the output occurs before
the process exits.
Still get a couple warnings... We don't really care about the
unlimited-use warnings from clojure.test, and there are a couple
warnings we get stemming from bugs/limitations in Eastwood.
This mainly addresses the fact that the following two commands generate
different output:
$ lein pom
$ lein with-profile default pom
I believe the problem also affects uberjar, since both tasks unmerge
:default prior to doing their thing.
Version 2.3.4 generates the same output for the above two commands,
because it doesn't expand profiles in the with-profile task, as master
does. So this change attempts to only deal with fully-expanded profiles
when [un]merging them.
By default, leiningen makes the following transformation:
lein TASK_NAME --help → lein help TASK_NAME
For tasks that implement a help, this is inconvenient. This patch
disables this transformation for task vars and alias values marked with
the meta: :pass-through-help true
