Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Compatibility with lein1 and lein2 #1

Merged
merged 3 commits into from Oct 3, 2012
Merged

Conversation

dgrnbrg
Copy link

@dgrnbrg dgrnbrg commented Oct 1, 2012

I've made a couple changes that depend on the yet-to-be-released version of leinjacker (tentatively 0.3.0-SNAPSHOT). This should allow sleight to work on lein1 and lein2. Take a look, and as soon as leinjacker gets released, hopefully these changes can go in to sleight.

…ing its changes to project.clj overwritten by a subtask

lein2 merges and unmerges profiles in a difficult-to-discover way,
which is why dependencies must either be injected directly at
eval-in-project, or else this extra work with profile management must
be done.
@dgrnbrg
Copy link
Author

dgrnbrg commented Oct 3, 2012

Leinjacker 0.3.0 has been released, so the portable hook-eval-in-project functionality can be used in a deployed version.

I've also written some code to safely include the injection in the project map, so that it works with lein2 profiles. For now, I'm using similar code in guzheng to ensure that modifications to the project map persist through arbitrary subtask chaining. Ultimately, this could be added to leinjacker, which would then make lein-sleight lein1 and lein2 compatible.

I think that these changes are suitable for merging, as they don't change any existing behavior, but they pave the way for lein1 and lein2 portability.

ztellman added a commit that referenced this pull request Oct 3, 2012
Compatibility with lein1 and lein2
@ztellman ztellman merged commit 6ccd89c into ztellman:master Oct 3, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants