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

[jponge]

Discussed in #833

^{Originally posted by ljtfreitas January 29, 2022}
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's declare 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]

Confirmed, an open module is open for deep reflection, but this does not mean that all packages get exported.