On 3/06/10 8:52 AM, Philip Crotwell wrote:
Hi I want my distribution to include the gradle wrapper, which is a very cool feature. That way anyone that wants to play with the source can do so with an easy build and no manual downloads even if they have never heard of gradle, great. I also want the tar to have the version in the tar filename as well as the directory it generates, say myProject-1.0.tar.gz untars to ./myProject-1.0. The trouble is that when a user tries gradlew in this directory, the projects name is myProject-1.0, the version is 1.0 and so the generated jar file is myProject-1.0-1.0.jar with doubled version numbers. Name is a read only property, so I can't set it in the build.gradle I am supplying. I have found that you can set the project name in settings.gradle, but also that settings.gradle is supposed to go away at some point. Is settings.gradle the best way to handle this?
It is at the moment. The settings.gradle file will go away eventually, but for now, this is the way to set the project name.
It seems a bit weird to have a whole separate file just to change the name.
This is one of the reasons we want to merge the settings.gradle into the build.gradle.
I suppose I could change the version in build.gradle to be "", but that seems weird as well. Has anyone else made use of the gradle wrapper in distributions? Is this a reasonable use of it?
We do exactly the same thing for the Gradle build. -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
