Miko

@nshmyrev Any chance the Maven Central package can be updated to 0.3.50? It's still 0.3.45. https://mvnrepository.com/artifact/com.alphacephei/vosk

@RealMangorage Thanks, but I suggested using a `module-info.java` because I was hoping the maintainers would decide in the future what packages would be exported, I only wrote it so that...

> The reason I haven't acted on this is that I have never used java modules before. > > I also don't see the need to restrict usage of anything...

@devoxin Hi, I do not know if you have more experience with Java modules, but given the above reasoning, would you be willing to merge this pull request?

@topi314 I decided to look more deeply into what packages should be exported, and I suspect that `com.sedmelluq.discord.lavaplayer.natives.*` and all the sub-packages within that are not meant to be exported?...

> unexporting anything would be considered a breaking change now. Okay, that's fine - I'll just simply continue to export all packages. Nonetheless, it's much easier to access the library...

> Java doesn't *require* that anyways for module support.... It does if you want to access the library through module path, and also being able to import the entire library...

> It lets you use either or, both put it onto the module path, Ive already been there and done that. I'm not familiar with how to do it in...

Well that is the reason for this pull request, to convince the devs that a module-info file would be beneficial. Of course if they don't want to merge it they...

@topi314 Hi, I'm sorry to bother you again. I understand you do not have much experience working with the Java module system, but I would like to ask if there...