Hey guys :) Just noticed that the Jvm class got moved into a different 'internal' package.
The stuff from that package is semi-private. On one hand it's private because we don't expose it in our javadoc. On the other, the package is imported by default (not to mention that it does not contain 'internal' in the name). I bet that bunch of our users' builds are using it, especially when the utility class is useful (just like Jvm is). I'd suggest that we develop some kind of strategy for slowly internalizing those classes (with the proper deprecation, etc.) or maybe leaving some of them public if it makes sense. Thoughts? -- Szczepan Faber Principal engineer@gradleware Lead@mockito
