Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Leiningen strangely broken #25

Closed
gilaras opened this issue Mar 11, 2010 · 2 comments
Closed

Leiningen strangely broken #25

gilaras opened this issue Mar 11, 2010 · 2 comments

Comments

@gilaras
Copy link

gilaras commented Mar 11, 2010

Leiningen (from git) is strangely broken. Apparently even downloading a clojure-contrib 1.1.0 dependency breaks something in ~/.m2 and leiningen is broken afterwards. To reproduce the problem take a look at:
http://gist.github.com/329308
@S11001001
Copy link
Contributor

The problem is that the lein script always puts clojure-1.1.0.jar from the Maven repo, if and only if it is present in said repo at the time of running lein, into the bootclasspath. This conflicts with the clojure-contrib AOT-compiled modules, which must be run with the Clojure classes from 1.2.0-SNAPSHOT in HEAD.

@gilaras
Copy link
Author

gilaras commented May 8, 2010

apparently fixed.

technomancy pushed a commit that referenced this issue Nov 3, 2023
Merge pull request 'Improved error reporting in search task' (#25) fr…
943e04c 
…om rome-user/leiningen:search-patch into main

Reviewed-on: https://codeberg.org/leiningen/leiningen/pulls/25
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gilaras @S11001001