Issue with the new mutiny module-info.java (1.3.1)

[ljtfreitas]

Hi all 👋 ,

I'm working in a library that depends from mutiny. I'm using 1.2.0 version, and my module-info is:

module my.module {

    requires io.smallrye.mutiny;
}

And all it's working as expected. So, I'm trying to update to 1.3.1 version from mutiny, and now my compilation is failing because, since 1.3.0 version, mutiny does not export packages anymore; instead, it declares the module with the open directive.

As far as I know about Java modules (not so much, I need to say :) ), a open module indicate that public types of the module are accessible, but just in runtime, not for compile time.

So, how can I fix this in order to upgrade the version? 🤔

Thank you so much, people.

[jponge]

We indeed decided to open all packages.

What compilation error are you getting?

[ljtfreitas]

Hi @jponge , thank you. The errors are:

error: package io.smallrye.mutiny is not visible

import io.smallrye.mutiny.Uni;
                  ^
  (package io.smallrye.mutiny is declared in module io.smallrye.mutiny, which does not export it)

same error for Multi

error: package io.smallrye.mutiny is not visible

import io.smallrye.mutiny.Multi;
                  ^
  (package io.smallrye.mutiny is declared in module io.smallrye.mutiny, which does not export it)

I'm thinking about add --add-exports=io.smallrye.mutiny/io.smallrye.mutiny to my compilation options, but...it will be just a hack, right? 😬 Is there a more elegant way to solve it?

Thank you!

[jponge]

Ok this has to be investigated, it may be us doing a wrong JPMPS module descriptor, or even not understanding the spec properly 😆

[jponge]

I opened #835

[jponge]

See #836

[ljtfreitas]

I see. JPMS is great but could be a bit tricky hehe 😆. Thank you @jponge

[jponge]

This has been fixed and will be part of Mutiny 1.4.0: #836

Meanwhile you can grab snapshots using version 999-SNAPSHOT from the Sonatype OSS repos.