Caleb Cushing

A matter of java's opinion 3. If a module is in the `to` then it must appear in the compiletime classpath, otherwise you get this warning. It's only a warning...

> I don't know what you mean by "in java9 instead". you can put a module-info in src/main/java9 instead of java and then it isn't supposed to affect java 8...

> You can put it anywhere you want. I'm not really familiar with what they're doing or how the build is structured. I also haven’t looked at that graphic in...

Okay, so we're on the same page with that. @autonomousapps are you getting this at all? Or are we completely not making any sense.

I've tried some his stuff (the testing plugin), I personally don't care for it. It has caused more problems than it's worth. In fact the other day I couldn't figure...

Oh, if you're asking if it has useful code to determine this? The answer is probably.

I'm "about"(tm) to write a blog post on modularization; which is why I clicked on this issue. This creates some levels of concern without more information though. I imagine such...

right, but as you mention "gist" and "assume" java has an `interface` and some people suggest that you should only exposes interfaces. Some people also make api jars that only...

there are alternatives that aren't jspecify. It's just one such set of annotations. > as virtually none of the Java world already work with them. actually almost all of the...

> Although I wouldn't care if another JPMS compatible library was used. I also said that. I think you are trying to twist my words. > That said, you can...