Fork me on GitHub
#leiningen
<
2019-10-31
>
erik12:10:46

without specifying any LEIN_JVM_OPTS or equivalent, does lein actually pass --illegal-access=permit to java by default?

alexmiller12:10:26

not to my knowledge

👍 4
erik13:10:29

oops, I seem to be stupid. apologies, nvm. 🙂

erik13:10:41

quick hacks from the distant past...

drewverlee18:10:53

so in https://github.com/technomancy/leiningen/blob/master/doc/MANAGED_DEPS.md#managed-dependencies it explains the goal is to > The idea is to provide a way to specify a version number for common library dependencies in a single location, and re-use those version numbers from other discrete maven/lein projects. But how does what you specify in :managed-depdencies do that? I can think of only one place. My ~/.lein/project.clj config that oversees "multiple projects" but thats just on a per computer basis. Is there a way for lein templates to build/reference each other in another way?

drewverlee18:10:40

like can you point a lein project at a master project somewhere (a project.clj stored in s3) and it specifies these managed dependencies?

drewverlee18:10:12

it seems the rest of the docs explain the answer lol

mikerod19:10:43

@drewverlee yeah a few plugins out there to do it in various ways.

mikerod19:10:52

lein-parent is my favorite

mikerod19:10:03

lein-modules also exists.