Which warnings do you want to suppress?

205

probably just for a couple months, but i need to transition a large codebase, it's not going to happen overnight, and more generally i'm not sure that I want to strictly follow ALL polylith guidelines, its very opinionated, maybe like 90%, TBD

Code that doesn't live under a top namespace, will not be recognised by the poly tool, and a consequence of this is that it will not recognise changes of your code either, which means that your code may not be tested properly, and it will also not appear in the info command. A dirty solution is to create a src directory in a project, and then move all your code there. The poly tool doesn't check code that lives in projects (and that is why the documentation says you should avoid putting code there). With this "trick" you can start to extract your code into bricks from there, without the 205 warning. With that said, my advice is still that you try to move all your code into components and bases.

i think i sort of get the gist of it,

(mapcat (fn [[k v]]
                  (if (:local/root v)
                    (:paths v)))
                (:libs basis))

there we go

The poly project itself does this with a "lifted basis" - see the build.clj file on GitHub

Oh, wait, lifted basis is for source for jar file inclusion

You don't need any tricks for AOT - it is transitive

At work we just aot the main ns

you need to pass the right src-dirs (?) and a list of all namespaces to ns-compile (?) to b/compile-clj before calling b/uber

hence the code snippet above

If code is on the classpath, you only need to specify the main ns.

You only need src-dirs if you ask it to AOT everything -- but since it is transitive, there's no point in doing that.

Unless you are dynamically loading certain nses -- and even there you can just specific those to be AOT'd along with you main entry ns.

ah ok gotcha

Again, see the build.clj in the poly project.

yah i’m using juxt clip which specifies a system of components in a edn file so there may be some extra logic i’ll need

that explains it

With the JAR file -- for a library -- you have to "lift" the basis so that you gather up all the source from the project since there's no transitive compile. But you also have to decide whether to include git deps (since the generated pom.xml can't refer to those).