Mordant 2.0 about mordant HOT 8 CLOSED

I can confirm it works, thanks a lot @ajalt

from mordant.

Hi @ajalt, stumbled over your library, looks pretty promising 🙂 I am wondering if you plan to break all the experimental interfaces until 2.0 or if they are already safe to use.
Also, I would like to use it in a JS project. I read here #3 that you are waiting for a PR to be merged. As far as I can see it is but the corresponding change not yet publish. So I guess you still wait for JetBrains? Any chance you publish an artifact consumable by a JS project beforehand?

from mordant.

@robstoll version 2.0.0-beta1 was just released with JS support. There shouldn't be any more major API changes, so give it a try and let me know if it works out for you,

from mordant.

Unfortunately I cannot try this, though I'd like to. Maven can't resolve it due to the missing colormath JARs. Will try it out when that's fixed! The functionality looks great. I'm not sure if it's worth limiting the library too much for JS and Native. At least, the JVM version can be compiled to fast native binaries using GraalVM now. And I'm not sure there is much use for this in the JS world, which has similar libraries already.

from mordant.

Colormath is definitely published; maven central might have had an outage when you tried.

The JS target isn't designed to be used as an npm package from pure JS; it's targeted towards projects written in Kotlin/JS. Other node libraries exist, but mordant should be the best to use from Kotlin.

from mordant.

OK, it works with Maven (the tool) if you specify mordant-jvm as the artifact ID instead of just mordant. The reason is, the mordant/colormath POMs are empty, as are the javadoc JARs published alongside them.

I think what's happened here is that Gradle/Kotlin MPP is publishing POMs that aren't actually usable by Maven but in such a way that Maven itself doesn't notice there's anything wrong. It then generates a useless/misleading error message. I suspect this is a side-effect of the desire to use Maven Central as a CDN which would normally insist on having a JAR and a POM, but Gradle wants to only publish its own JSON module file, so it ends up making these empty files. Not ideal.

I think the fix is to provide separate instructions for Maven users that contains the JVM specific artifact, as Maven cannot read the multi-platform lib metadata anyway. I'll open a quick PR.

from mordant.

Hello @ajalt
could you notify me when intellij/markdown and therefore mordant is available on Kotlin/Native?
I want to integrate it to my starter project for building command line tools

https://github.com/jmfayard/kotlin-cli-starter

from mordant.

Mordant 2.0.0-beta2 has been released, which includes macosX64 support (@jmfayard)

from mordant.