yogsototh/leiningen
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

PROFILES.md: Tip to use composite profile

Browse source 
Sometimes we need to override *parts* of a prticular profile on a project-specific base. To a novice
lein user, it is likely not clear how to achieve this. This tip points her in the right direction -
using a composite profile with a "personal" part that can be overriden in `profiles.clj` to change
what is in the "common" part of the profile.
This commit is contained in:
Jakub Holy 2014-04-24 08:27:15 +02:00
parent 08b0dcb64b
commit 0d7932f994
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/PROFILES.md
View file

@ -89,8 +89,11 @@ to have a single version of a given dependency present at once). The
replace/displace metadata hints still apply though. replace/displace metadata hints still apply though.
Remember that if a profile with the same name is specified in multiple files, Remember that if a profile with the same name is specified in multiple files,
the last one will *replace* the previous ones, no merging. Only profiles of the last one will *replace* the previous ones, no merging. (If you need to enable
different names are merged onto the project map. personal overrides of parts of a profile, you can use a composite profile with
common and personal parts - something like `:dev [:dev-common :dev-overrides]`;
you would then have just `:dev-overrides {}` in `project.clj` and override it in
`profiles.clj`.)
Another use of profiles is to test against various sets of dependencies: Another use of profiles is to test against various sets of dependencies: