Fixes build_release.sh issue when using leiningen v2.3 #670
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If it's backwards compatible let's take out the min-lein-version |
|
@nathanmarz Done. Tested on leiningen v2.3.2 and v2.2.0 |
…without jar files. This fixes it by forcing lein to store jar in the same path it use to, target/... instead of target/profile-name/...
|
Fyi, my Author changed Author: Jason Jackson [email protected] |
|
it's a pain in my setup to flip these back and forth. |
nathanmarz
added a commit
that referenced
this pull request
Aug 29, 2013
Fixes build_release.sh issue when using leiningen v2.3
|
@nathanmarz I find the git history to be not so useful. commit 85895c8 commit 46cc0fc If you asked people to rebase their commits before merging it would clean this up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
latest version of leiningen breaks bin/build_release.sh creating zip without jar files. This fixes it by forcing lein to store jar in the same path it use to, target/... instead of target/profile-name/...
Steps to reproduce: