On 22/03/2012, at 2:51 AM, Szczepan Faber wrote: > 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?
Let's deprecate the old Jvm class, then. At some point we'll make some kind of Jvm domain model available to builds, but that can wait. It's not simply a matter of making the current Jvm class public. It needs some rework before then, to better separate the jre and jdk concepts, get rid of the statics, convert to an interface, and so on. @Rene, can you add an empty deprecated org.gradle.util.Jvm extends org.gradle.internal.jvm.Jvm, and note the deprecation in the migration guide, please? -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
