Forgot to add, you can then run `lein repl` from my-proj as usual, and have
easy access to your library code:
~~~
$ cd ~/dev/my-proj
$ lein repl
> my-proj.core=> (my/foo 4)
4 Hello, World!
nil
~~~
On Thursday, March 12, 2015 at 11:58:53 AM UTC-4, John Gabriele wrote:
>
> Hi Cecil,
>
> I think w
Hi Cecil,
I think what you want to do is create a library project to house your
common code, install the library to your local repository, then use it from
your project:
~~~
cd ~/dev
lein new my-stuff/my-lib
cd my-lib
# edit src/my_stuff/my_lib.clj , adding your common code here
lein install
#
Putting them in the working directory does not add them to the classpath.
Leiningen used to have an 'escape hatch' to allow local libraries to be
added to the classpath, but that was removed. The right way to do it now is
to make the artefacts you want on the classpath available to Maven. The
e
2015-03-12 12:00 GMT+01:00 Hildeberto Mendonça :
> $ cd ~/Clojure
> $ lein repl
>
> Your code in the repl will see the path ~/Clojure as working directory, so
> any file there will be accessible to your code by simply using the name of
> the file. If you have sub-directories then add the relative
$ cd ~/Clojure
$ lein repl
Your code in the repl will see the path ~/Clojure as working directory, so
any file there will be accessible to your code by simply using the name of
the file. If you have sub-directories then add the relative path:
"path/to/the/file/the-file.txt"
On Thu, Mar 12, 2015 a
I have some files in:
~/Clojure
that I want to use in a project I start with:
lein repl
But I do not see how to do this. How can I acomplish this?
--
Cecil Westerhof
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, sen
