cljdoc

2022-03-22T10:24:52.804819Z

I'm having some kind of bizarre problem building a documentation

✅ 2
lread 2022-03-23T19:49:26.855339Z

Looks like you are all good now @huxley?

2022-03-23T19:49:47.513879Z

yes

2022-03-23T19:49:52.797599Z

thx

👍 1
2022-03-23T19:50:36.281989Z

I had to learn how to build proper jar packages

lread 2022-03-23T19:51:05.211179Z

Cool, glad you figured it all out!

2022-03-23T19:51:11.714809Z

thanks again for your help

lread 2022-03-23T19:51:26.309009Z

You are most welcome!

2022-03-22T10:25:56.419069Z

whatever I want to build, I always get the error

Could not locate xyz on classpath

2022-03-22T10:26:22.103249Z

the problem is that xyz are not dependencies, but the library itself

2022-03-22T10:28:15.631189Z

the problem is with the api analysis,

lread 2022-03-22T12:48:33.225359Z

I'm happy to have a peek sometime today @huxley, can you provide a link to the failing build?

2022-03-22T13:16:26.821509Z

@lee https://cljdoc.org/builds/55413

lread 2022-03-22T14:38:09.874659Z

@huxley I downloaded fatum-0.0.14.jar and unzipped it to get:

$ tree fatum-0.0.14 
fatum-0.0.14
├── META-INF
│   ├── MANIFEST.MF
│   └── maven
│       └── com.github.ribelo
│           └── fatum
│               ├── pom.properties
│               └── pom.xml
├── main
│   └── ribelo
│       ├── fatum
│       │   └── Fail.java
│       └── fatum.cljc
└── ribelo
    └── fatum
        └── Fail.class
The sources under main seems suspect to me. Maybe you have a packaging problem?

2022-03-22T14:45:48.510879Z

the java environment is completely unknown to me, I am in the JS ecosystem on a daily basis

lread 2022-03-22T16:41:33.644319Z

The reason fatum.cljc is not found it because a load is attempted for it at under ribelo but it is sitting under main/ribelo.

lread 2022-03-22T17:06:14.698689Z

One thing you might try is is to test locally against your built jar. Just as a normal user of the library.