Fork me on GitHub
#polylith
<
2024-02-21
>
rpatrelle21:02:21

I asked at first this question in #C1Q164V29 chan. But according to discussion with @seancorfield, this is a Polylith concern. We mainly run test locally in the repl. I tried to launch project test locally in a terminal but I am facing another issue, not allowing to reproduce.

tengstrand05:02:40

Could you create a PR with a minimal workspace under https://github.com/polyfy/polylith/tree/master/examples where you recreate the problem @U01BZRQA0ER? Then I can have a closer look + include it in the regression test suite.

rpatrelle18:02:36

@U1G0HH87L I will try to free time to do so.

rpatrelle18:02:31

Minimal workspace is not so easy. I want to create a workspace enough representative to our (big) project in order to reproduce. It implies at least 2 bases, 2 components and 2 projects.

tengstrand18:02:33

Sounds good!

rpatrelle17:02:00

Hi @U1G0HH87L, I worked on this example. But I am quite new to Polylith and I am facing an issue. Sounds my tests are not launched when I use poly test command. I have some log in my test setup but nothing is printed and it show 0s left for the test. I stored my code here: https://github.com/patinside/sql_classpath_issue Maybe something evident but did not catch yet the point.

tengstrand17:02:47

I will have a look.

šŸ™ 1
tengstrand17:02:13

I have a couple of questions @U01BZRQA0ER: ā€¢ Do you use the latest 0.2.19 version of the poly tool? ā€¢ Have you used the latest documentation for https://cljdoc.org/d/polylith/clj-poly/0.2.20-SNAPSHOT/doc/readme? You have added the bricks with extra-paths but it's better if you switch to :local/root which is described in the documentation. If you do that, then you can clean up your ./deps.edn file and move your libraries to each deps.edn file in your bricks. I could see that you had missed to add a few paths, but if you do these changes, then will be easier also to get it right!

tengstrand17:02:14

You can use :local/root like this:

rpatrelle17:02:42

I don't use the latest version of poly tool I think. How do you get the version (tried --version, -v) I used the tutorial in clojure-polylith-realworld-example-app repo. I will test your proposal. But I wanted to be as close as possible to our project. Do you think such configuration with extra-paths may impact the classpath issue we are facing?

tengstrand17:02:56

You could try to use the latest version of the poly tool, together with the :local/root syntax, and see if it helps. It should clean up your code at least!

rpatrelle17:02:13

Ok, will do

šŸ‘ 1
tengstrand17:02:25

If you still have problems, then we can continue from there.

tengstrand17:02:41

And remember, if you use Cursive, you need to follow the instructions https://cursive-ide.com/userguide/polylith.html.

rpatrelle17:02:58

I am on vscode with Calva

tengstrand17:02:15

Okey, they you should be fine.

tengstrand18:02:28

Try to move your libraries into the bricks where they belong also, so that you don't have do specify them again in all your projects.

rpatrelle18:02:44

oh, I use a not so old poly: 0.2.18

rpatrelle18:02:00

sound this is the lastest available with homebrew, isn't?

tengstrand18:02:49

You can begin with 0.2.18, and if you still have problems, try using 0.2.19.

rpatrelle18:02:19

Works better with :local-root syntax. I am now facing some strange issue regarding the deps. For the data-api base, I have to require HikariCP while it is used in the sql component and declared in the component deps.edn. Same for hugsql .

tengstrand18:02:57

That sounds strange. Maybe you can reproduce that in your repository that you shared?

rpatrelle18:02:20

yes, i will commit

šŸ‘ 1
tengstrand18:02:20

Okay, will have a look.