I'd like to improve the package organization of the Gradle source code.
The original idea was to have an org.gradle.api root package under which all the interfaces lies that are supposed to be used by Gradle users. org.gradle.api.internal contain the implementations and helper classes. The infrastructure code for running a Gradle build lies under the org.gradle root package.
I think this does not make sense any longer. From an embedded perspective the infrastructure is as much api as the stuff under org.gradle.api. And you also want to hook into the lifecycle from your build script. Therefore I think it makes sense to get rid of the api package all together.
We would end up with org.gradle and org.gradle.internal as root packages. Starting to extract parts of the code base into separate subprojects (e.g. wrapper) would also help in cleaning up things.
Thoughts? - Hans -- Hans Dockter Gradle Project Manager http://www.gradle.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
